Anyone know why this is happening? I can not upgrade my game now, the build will not work due to this...which i dont know how to get it to BE private again?
APK signing failed! Key associated with user not a private key
I mean this is a huge issue, no one has this, or is aware how to fix?
u have to use same key which is used for version 1,
and change build version to 2.0 in case uploading the new apk to same bundle identifier .
I do, it gives that error.
APK signing failed! Key associated with Adrenaline not a private key
APK Signing Failed!
jarsigner: key associated with adrenaline not a private key
PostProcessAndroidPlayer:SignAndroidPackage(String , Single, Single&)
PostProcessAndroidPlayer:PostProcess(BuildTarget, String, String, String, String, String, String, BuildOptions)
Come on, no one has any clue??? I mean none?
I got this issue too, for no obvious reason .
1. I have deleted all information about my keystore/public key etc.. from the player settings
2. Close Unity and delete my keystore
3. Restart Unity, create a new Keystore
Hope this help
Same problem... Someone solved it?
Unity version: 3.5.0b6
same problem... it seems now that it works though.. changed the version to 2 but also in the meanwhile tried to create a new key.. that did not let me update the app online... choose the old key again and then it seems to have worked... uploading it now to see if it has actually worked... hope this helps someone.
jarsigner: key associated with <keyname> not a private key
There can be several reasons for that messages, the most common one is that the key password is wrong. OBS! Not the password for the key storage but the password for the actual key.
Same here. Is this a known unity bug? Tried to clean all data related to my key but with no success. Any ideas?
I had this same issue. It was as bitter said, wrong password. I don't think it's a Unity bug, just a chair to keyboard interface problem. ^_^
It was lost forever and I had to make a new build.
NEVER LOSE THIS INFO OR YOU WILL BE SCREWED!@
Hi, I just wanted to let you know that for 3.5.7 and 4.0 we did a major cleanup in regards to how we handle apk signing. Hopefully this will solve any problems previously related to different versions of java and/or different signing algorithms. The fix should also provide you with more detailed error messages as to what the problem is when the apk fails the signing process.