Certificate chain not found, how to fix and publish to Google Play Store?

Question

ERROR MESSAGE:

jarsigner: Certificate chain not found for: project_foo.

project_foo must         


        

Answer 1

The Developer on our team proposed the solution that fixed the problem. Previously I had copied the Foo.apk into the directory with the jarsigner.exe and tried to run it there. He proposed:

1. Set the PATH environment variable so Windows can find the jarsigner executable.
2. Move the Foo.apk to the path where the keystore was located.
3. Run the command below (without using a path to find the keystore).

jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore .keystore Foo.apk project_foo

It works! Removing the necessity to specify file path for the keystore fixed the problem.

Answer 2

i had the same issue my commands were

to generate key

 keytool -genkey -v -keystore testapp-key.keystore -alias testapp-key -keyalg RSA -keysize 2048 -validity 10000

and then i did this to sign the app

jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore testapp-key.keystore testapp.apk testapp

i got this error

jarsigner: Certificate chain not found for: testapp.<br/>
project_foo must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.

then i replaced the alias 'testapp' in the jarsignir command with the key alias that is 'testapp-key' it is in first command i.e. key generation command

the command will look like this

jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore testapp-key.keystore testapp.apk testapp

in your case it will be like this

 jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore C:\Path\\.keystore Foo.apk your-key-alias

Answer 3

you have to name your signed App like alias name

for example:

if you have this name "myFirstSignedApp" as alias then you have to determine this name in jarsigner command

jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore testapp.keystore app-release-unsigned.apk myFirstSignedApp

Answer 4

If you are trying to sign your .aab or .apk ,from Android Studio but keep getting this error even though you are doing everything right, here is the solution that worked for me: Go to search and find Command Prompt. Run it as Administrator. Now Type this line.

"C:--->Your Path To jarsiner<---\jdk1.8.0_192\bin\jarsigner" -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore "C: **--->Your Path To the Keystore<---**\Desktop\OfficalBuilds\MyKey.keystore" "C:**--->Your Path To the .apk Or .aab<---**\Desktop\MyFinalBuild.aab"  "My Alias "

If you tried the above solutions,you will notice now the alias is typed inside " ". Also sometime there is a space at the end "My Alias "

Answer 5

keytool -keystore formconnect.keystore -list -v

You can use this command to find out your alias name after you have generated your key.

First line of execution contains the Alias name: <value> If keytool is used then alias name might be "mykey".

Use that alias name while packaging the application.

Answer 6

add release unsigned.apk folder path

jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore keystorename.keystore .....\platforms\android\build\outputs\apk\android-release-unsigned.apk aliasname

it's work for me !!