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

Unity Engine
,
1

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

I mean this is a huge issue, no one has this, or is aware how to fix?

3

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

I do, it gives that error.

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

5

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

Come on, no one has any clue??? I mean none?

7

great forum

8

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

1 Like
9

Same problem… Someone solved it?

Unity version: 3.5.0b6

10

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

jarsigner: key associated with 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.

1 Like
12

Say even if removing all the info from the Publishing settings helps to workaround this issue, what do you do to bump into it?

13

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

14

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. :slight_smile:

1 Like
15

It was lost forever and I had to make a new build.

NEVER LOSE THIS INFO OR YOU WILL BE SCREWED!@

1 Like
16

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.

17

I know this is old, but I have Unity 2019.2.5 and still have this issue. All I can do to fix it is get a new keystore, which is not the best way to do things for updates. Last time this happened, I had to completely remove my app from the Play Store and start over. Is there a fix for this yet?

18

As previous posts point out, the problem is not with Unity. You are entering wrong password for your key.

1 Like
19

I’m experiencing this issue myself, however the password is 100% correct (since it’s the same as with the keystore and i’m simply copy pasting). So what else could it be? I’m attaching the Editor log just in case but here’s the relevant parts

1 exception was raised by workers:
java.lang.RuntimeException: jarsigner.exefailed with exit code 1 :
jarsigner: key associated with <> not a private key

So what could it be?

5321814–535575–Editor.txt (1.82 MB)

20

Hope You Can See This