Unity Community


Results 1 to 16 of 16

  1. Location
    DC
    Posts
    387

    APK signing failed! Key associated with user not a private key

    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


  2. Location
    DC
    Posts
    387
    I mean this is a huge issue, no one has this, or is aware how to fix?


  3. Location
    Hyderabad,India
    Posts
    211
    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 .


  4. Location
    DC
    Posts
    387
    I do, it gives that error.

    ERROR!
    APK signing failed! Key associated with Adrenaline not a private key


  5. Location
    DC
    Posts
    387
    APK Signing Failed!
    jarsigner: key associated with adrenaline not a private key

    UnityEngine.Debug:LogError(Object)
    PostProcessAndroidPlayer:SignAndroidPackage(String , Single, Single&)
    PostProcessAndroidPlayer:PostProcess(BuildTarget, String, String, String, String, String, String, BuildOptions)
    UnityEditor.HostView:OnGUI()

    anyone?


  6. Location
    DC
    Posts
    387
    Come on, no one has any clue??? I mean none?


  7. Location
    DC
    Posts
    387


  8. Posts
    1
    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


  9. Posts
    6
    Same problem... Someone solved it?

    Unity version: 3.5.0b6


  10. Location
    Mount Pearl, Newfoundland
    Posts
    85
    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.

    Jason

  11. Android Mechanic



    Location
    Stockholm, Sweden
    Posts
    198
    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.
    - Martin

  12. Super Moderator
    Location
    Vilnius, LT
    Posts
    662
    Say even if removing all the info from the Publishing settings helps to workaround this issue, what do you do to bump into it?
    I know about iOS, Android, Flash and something else
    personal blog: drinkandcode.com
    twitter: iWozik


  13. Posts
    34
    Same here. Is this a known unity bug? Tried to clean all data related to my key but with no success. Any ideas?


  14. Posts
    5
    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. ^_^


  15. Location
    DC
    Posts
    387
    It was lost forever and I had to make a new build.

    NEVER LOSE THIS INFO OR YOU WILL BE SCREWED!@

  16. Android Mechanic



    Location
    Stockholm, Sweden
    Posts
    198
    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.
    - Martin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •