APK signing error : Failed to read key from keystore

Question

I'm developing android app under intellij and gradle. and using following way to generate keystore file:

keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000

then used the keystore file in build.gradle:

signingConfigs {
    robert {
        storePassword 'robert'
        storeFile file('/Users/bournewang/Documents/Project/android.keystore')
        keyPassword 'robert'
        keyAlias 'mike'
    }
}

when finally trying to generate signed apk file: ./gradlew assembleRelease

it gives the error:

Execution failed for task ':Myexample:packageRelease'.

Failed to read key from keystore

adding --info and --stacktrace to the gradlew command line should give you more info that might help pinpoint the problem. — Scott Barta, Dec 10 '13 at 17:12
I was facing this because the "key alias" I typed in didn't exist in the keystore. [This answer](http://stackoverflow.com/a/28119723/1276636) helped me out. — Sufian, Mar 10 '15 at 06:22
Changing Gradle JDK verison helped me try this -> [View](https://stackoverflow.com/a/76000947/13651898) — Supun Ayeshmantha, Apr 13 '23 at 01:25

score 91 · Answer 1 · edited Dec 05 '17 at 11:41

91

In order to find out what's wrong you can use gradle's signingReport command.

On mac:

./gradlew signingReport

On Windows:

gradlew signingReport

edited Dec 05 '17 at 11:41

Amt87

5,493
4
32
52

answered Mar 09 '14 at 07:46

Tom Susel

3,397
1
24
25

+1 thank you for that hint! This way I figured out, that when running signingReport it did list my release signing config, but only the Store location, the variant, the config and the alias. It was missing Sha1, md5 and the valid until. The reason was: my alias was wrong : ) - so if above command lists the entire set of info, you should be all set (variant, config, store, alias, md5, sha1, valid until), if not, make sure you have passwords, keystore and alias set up correctly in your project's build.gradle file – AgentKnopf Jan 20 '15 at 09:22
1

Running this it is showing that: `Variant: release Config: none` Is my .keystore deleted? – Shajeel Afzal May 26 '15 at 20:23
thanks a bunch! gradlew is located directly in ones android studio project directory. Calling signingReport reveals that the debug-key's alias is actually "AndroidDebugKey"... – hotzen Jun 04 '15 at 20:24
Or for me it was (in the android platform director) ./gradlew.bat signingReport – csga5000 May 11 '16 at 22:20
I had the wrong alias and got a result with no errors but not the desired data, so for those who at first didn't know how o interpret the report, your key MUST be print with SHA1 and MD5 values next to it to consider it correct. – Felipe Sabino Jun 29 '16 at 11:54
This saved me a lot – Idris Stack May 07 '20 at 08:37
Guys i've got this error and i don't know how to solved it. Error: Failed to read key android-production from store "/Users/rodrigodiasdefigueiredo/Desktop/z-mobile/android/app/android-production.keystore": Get Key failed: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. – Rodrigo Dias Aug 02 '23 at 10:00

score 75 · Accepted Answer · answered Dec 10 '13 at 16:22

Check your keystore file for first, in you example you creating file with name my-release-key.keystore. If its correct and really present in folder Users/bournewang/Documents/Project check alias, in your example it is -alias alias_name, but in config you specified alias mike

score 9 · Answer 3 · edited May 23 '17 at 11:33

9

Most likely that your key alias does not exist for your keystore file.

This answer should fix your signing issue ;)

edited May 23 '17 at 11:33

Community

1
1

answered Mar 10 '15 at 16:37

Stephen Vinouze

1,815
1
17
28

why there no option in my android studio ver 4.0.1 – Mike Victoria Sep 07 '20 at 03:51

score 6 · Answer 4 · edited Jan 22 '20 at 17:03

6

Removing double-quotes solve my problem, now its:

DEBUG_STORE_PASSWORD=androiddebug
DEBUG_KEY_ALIAS=androiddebug
DEBUG_KEY_PASSWORD=androiddebug

edited Jan 22 '20 at 17:03

Aniruddh Parihar

3,072
3
21
39

answered Feb 26 '17 at 12:02

fincode

104
1
3

46

Where did you remove?? In the sky?? – sajid Jul 10 '19 at 08:00

score 4 · Answer 5 · answered Aug 28 '17 at 12:24

4

In my case, while copying the text from other source it somehow included the space at the end of clipboard entry. That way the key password had a space at the end.

answered Aug 28 '17 at 12:24

Stjepan Golemac

121
2
4

score 3 · Answer 6 · 2022-06-13T08:07:58.297

For me this worked.

Go to <your_app_name>/android.
On the terminal use ./gradlew signingReport for Mac OS and gradlew signingReport for Windows.
Check if each element of each task has a Variant, Config, Store, Alias, MD5, SHA1, SHA-256, Valid until. If so you should be good.
If any of the above are absent then try to regenerate the key store by following the instructions on this page.
Copy the key store file and paste it inside <your_app_name>/android/app.

Some things that I was doing wrong while generating the key store file were.

Using quotations on MYAPP_UPLOAD_..._PASSWORD's.

MYAPP_UPLOAD_STORE_PASSWORD="Password123"
MYAPP_UPLOAD_KEY_PASSWORD="Password123"

I used \J4ct@RD as a password and it did not work. I later changed the password to something that was just aplphanumeric and it worked.

score 2 · Answer 7 · answered Jun 10 '21 at 04:38

2

In Android Studio go to Build > Clean Project then re-generate signed APK using Build > Generate Signed Bundle / APK... and then clear password-fields and re-enter your passwords

answered Jun 10 '21 at 04:38

MTM

113
1
8

For those who typed alias wrong in the first time, and keeps getting the same error even if they changed the alias can try this. It worked for me. – Egemen Hamutçu Dec 22 '21 at 12:21

score 2 · Answer 8 · answered May 26 '23 at 05:45

2

In my case it happened in Debug build variant. So I closed the android studio. deleted the debug.keystore and debug.keystore.lock files and open the project again. That fixed my problem.

answered May 26 '23 at 05:45

Ehsan Shadi

609
6
17

you are a life saver – Kanjah Jun 07 '23 at 13:58

score 1 · Answer 9 · answered Feb 05 '19 at 07:28

For someone not using the signing configs and trying to test out the Cordova Release command by typing all the parameters at command line, you may need to enclose your passwords with single quotes if you have special characters in your password

cordova run android --release -- --keystore=../my-release-key.keystore --storePassword='password' --alias=alias_name --password='password'

score 1 · Answer 10 · answered Dec 12 '19 at 14:40

1

The big thing is either the alias or the other password is wrong. Kindly check your passwords and your issue is solved. Incase you have forgotten password, you can recover it from the androidStuido3.0/System/Log ... Search for the keyword password and their you are saved

answered Dec 12 '19 at 14:40

Daniel Nyamasyo

2,152
1
24
23

Could you kindly confirm if the Log file i should be looking at is this == idea.log , at the path == C:\Users\xxxx\.AndroidStudio3.5\system\log\idea.log – Rohit Dhankar Jan 11 '20 at 09:09

score 1 · Answer 11 · answered Mar 21 '21 at 22:44

1

Make sure you have correct the folliwn

keystore file path
keystore alies name
keystore password

keystore in android/key.properties

answered Mar 21 '21 at 22:44

Umer Waqas - Top rated dev

3,072
29
26

score 1 · Answer 12 · answered Jun 13 '21 at 12:29

1

in my case for some reason, after updating android studio to the last stable version, the password that was always by default got changed, i just had to set correct password again and it worked

answered Jun 13 '21 at 12:29

karique

533
6
17

score 1 · Answer 13 · answered Jan 31 '22 at 23:14

1

Depending on where you generated the keyfile, keytool might refer to a different binary, running on a different JVM version. These are not necessarily compatible, try adjusting the versions.

answered Jan 31 '22 at 23:14

phil294

10,038
8
65
98

score 0 · Answer 14 · answered Mar 05 '16 at 21:59

0

It could be any one of the parameter, not just the file name or alias - for me it was the Key Password.

answered Mar 05 '16 at 21:59

A-S

2,547
2
27
37

score 0 · Answer 15 · answered Mar 19 '21 at 07:08

I got same error today.

Execution failed for task ':app:packageRelease'. A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable com.android.ide.common.signing.KeytoolException: Failed to read key news from store "E:\keystore\news.jks": Keystore was tampered with, or password was incorrect

I had same key password and key store password. But i wrote a wrong password.

score 0 · Answer 16 · answered Jul 15 '23 at 15:41

0

for me was need to update the key when I transfer the source code to another PC

the steps using UI

files ==> Project Structure... ==> Modules ==>Sining Configs

answered Jul 15 '23 at 15:41

Hassan Badawi

302
1
10

APK signing error : Failed to read key from keystore

16 Answers16

Linked