Android studio Update bundle jarsigner: key associated with key0 not a private key

Question

These are the steps I am taking, in the order presented, to update a published app after fixing a bug, through Android studio:

Fix the bug.
Changed to versionCode 2 and versionName "1.1" on build.gradle (Module)
Generate Signed Bundle
Key-store path is C:\Folder\Folder\Android\MyApp.jks
Both passwords are correct
Key alias: key0 (default as on first time)

But then this error is raised:

Cause: jarsigner.exefailed with exit code 1 :
jarsigner: key associated with key0 not a private key

What could be causing this?

did you got any solution for this. I am too facing this issue after update android studio to 3.3 — Rakesh, Jan 24 '19 at 10:50
am still facing this issue, tried all the solutions mentioned here. am using andoird studio gradle plugin 5.1.1 — user93796, May 29 '19 at 16:14

score 15 · Answer 1 · answered Feb 28 '19 at 20:42

15

"Build" -> "Clean project", then "Generate signed ..." again - worked fine for me

answered Feb 28 '19 at 20:42

Koozy.ua

151
3

@user93796 are you having the same error ` Cause: jarsigner.exefailed with exit code 1 : ` ? – kvadityaaz Jun 05 '19 at 10:42
Simple but overwhelming! We should always clean the project to avoid possible errors like this. – IgniteCoders Sep 12 '19 at 07:33

score 7 · Answer 2 · edited Jun 20 '20 at 09:12

7

it's simply means that you enter wrong key let me explain

your password for keystore correct
you password for The key is't correct

edited Jun 20 '20 at 09:12

Community

1
1

answered Jul 15 '19 at 12:19

sf7k

99
1
3

the output can be deceiving. no issue with the key, just needed to double check the passwords – plosco Jul 24 '20 at 22:37

score 2 · Answer 3 · answered Apr 15 '20 at 18:33

I had the same issue, I have tried Clean Build and Invalidate Caches/Restart but didn't work. Finally I entered a Wrong KeyStore password then it has shown some error like jarsigner error: java.lang.RuntimeException: keystore load: Keystore was tampered with, or password was incorrect. Then I tried with the Original one and it worked.

score 1 · Answer 4 · answered Aug 28 '19 at 14:16

For those coming to this question to build a release candidate of a React Native app for the Play Store, or if building without Android Studio.

a) Cleaning the project is particularly useful if you've had previous errors in your release packaging:

cd android
./gradlew clean

b) Check to see if your keystore was created correctly, with a valid, exportable certificate embedded inside:

keytool -export -alias your-keystore-alias -file mycertificate.crt -keystore /path/to/keystore

You will be prompted for the keystore password you used when generating the keystore. If you get a mycertificate.crt file created successfully, there isn't anything wrong with your keystore. It's valid.

c) The not a private key error can also come up if you've not explicitly supplied a key password, and just a store password (as shown below), in your gradle release build properties:

MYAPP_UPLOAD_STORE_FILE=my-app.keystore
MYAPP_UPLOAD_KEY_ALIAS=my-app
MYAPP_UPLOAD_STORE_PASSWORD=keystorePassword
MYAPP_UPLOAD_KEY_PASSWORD=

When generating a signing certificate with keytool, there is an optional argument to generate a separate certificate password, apart from the keystore password. However, if no certificate/key password is supplied, it inherits the keystore password. So in this case, a working set of properties would be:

MYAPP_UPLOAD_STORE_FILE=my-app.keystore
MYAPP_UPLOAD_KEY_ALIAS=my-app
MYAPP_UPLOAD_STORE_PASSWORD=keystorePassword
MYAPP_UPLOAD_KEY_PASSWORD=keystorePassword

Thanks. Just updated `MYAPP_UPLOAD_KEY_PASSWORD=keystorePassword` and all work — Andrey Patseiko, Jun 11 '20 at 11:42

score 0 · Answer 5 · answered Jan 24 '19 at 19:51

Well i also faced this problem after upgrading to android studio 3.3 and i resolved in 3 steps. But firstly make sure you backup your whole project.

In Android Studio goto File > Project Structure and untick from "use embedded JDK" then click OK
Goto Computer Settings (system settings) (win + pause key) then go to Advanced system settings>Environment variables. if JAVA_HOME not present then add it and set path to your installed JDK. As i couldn't find a direct approach to modify jdk path in my project that is upgraded in some way to android studio 3.3 settings, i did following(for the last step) BUT MAKE SURE YOU MAKE BACKUP BEFORE THIS.
To make sure where i am guiding come to project view, I deleted ".grade", ".idea", "capture", "gradle" folders from the root and "build", "release", "lib" folder from "app" leaving "src" as it is. Deleted root.iml and did not delete app.iml file Then rebuild the project and then created the Signed package.

It went successful after 2 try. To be very honest i did the last step twice by restoring files from backup. As deleting these folders i messed up 1 time.

score 0 · Answer 6 · answered Jun 05 '19 at 11:06

0

It seems that you are entering wrong password if

"Build" > "Clean project"

doesn't solved your problem.

Try the reference link providing : Click here

answered Jun 05 '19 at 11:06

kvadityaaz

1,441
1
16
23

bam · Answer 7 · 2019-06-13T20:32:57.580

0

For those who had no luck with "Clean Project", try changing the key password with the following command in the Android Studio Terminal

keytool -keypasswd -alias yourAliasName -keystore pathToYourKeystoreFile

afterwards you're prompted for your keystore password and if correct can then change the key password.

I had the same issue, I have both passwords written on a piece of paper and all of a sudden (Android Studio update?) the key password didn't work anymore. Keystore worked, could select the alias, but when generating the signed app, same error as you got.

edited Jun 13 '19 at 20:32

answered Jun 13 '19 at 20:19

bam

302
2
10

when I run this command it asks for my password, when I put it In it just says "keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect" but if I try and bundle up my app in the wizard I enter the keystone password and its fine as it lets me select which key to work, then shows the error OP mentioned, any idea why this is happening? – AngryDuck Aug 13 '19 at 13:59

score 0 · Answer 8 · answered Jun 20 '19 at 08:06

0

After trying all the solutions here, it either did not work or was too complicated to even make it work.

In the end simply restarting my PC is what helped.

answered Jun 20 '19 at 08:06

Big_Chair

2,781
3
31
58

score 0 · Answer 9 · answered Aug 18 '19 at 04:58

0

Special characters in your password? Read on

(Not 100% sure but) I had special characters in my key password and I decided to remove all double quotes (") only because it might have been the culprit and it worked.

answered Aug 18 '19 at 04:58

reddtoric

568
1
6
13

score 0 · Answer 10 · answered Apr 14 '20 at 11:50

0

Take care of the numbers of caracters of your password : 6 min I have try more than 20 => this is ko 12 is ok

Don't use special car, caps, nums, are enought

answered Apr 14 '20 at 11:50

JMM MAS

11
4

Android studio Update bundle jarsigner: key associated with key0 not a private key

10 Answers10

it's simply means that you enter wrong key let me explain

Linked