I took over an existing Android app together with a keystore file to sign it, but signing and uploading the app causes the following error:
Upload failed
You uploaded an APK that is signed with a different certificate to your previous
APKs. You must use the same certificate. Your existing APKs are signed with the
certificate(s) with fingerprint(s):
[ SHA1: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX,
SHA1: YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
SHA1: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
One thing that's odd here is that the fingerprint of the certificate I used to sign the .apk file (XX) is listed the existing APKs fingerprints. Now I wonder, do I need to sign the APK file with a second certificate in order to be able to update it at playstore? I.e was the original version (the one currently in Playstore) signed twice? Is there any way to use only one of the two certificates for future updates?
Any clarification is welcome.
Thanks in advance.
please download KEYSTORE EXPLORER and open your .jks file with it and there you can see which certificate contains the signature you used to signed the apk in the play store.
Related
I have an app in the Play Store. I have updated the app three times earlier but never got the error while updating the apk. Now when I am trying to update the apk with the same fingerprint ".jks" file I am getting the below mentioned error.
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[SHA1: D1:------------------------------:7E ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: A2:------------------------------:31 ].
This issue is occurring because your update APK is signed with a different keystore than your old version (and for this reason has a different SHA1 fingerprint).
Resign your app with the right keystore and then reupload it to the Play Store.
See more information regarding signing your Android app before publishing here.
I need to update my app in google play store, but I generated apk file on another computer that the previous one. I used the same keystore file (lazymojo.jsk) and I get an error about using different SHA1 certificate. Then I switched to my old pc where i made the first version and generate signed apk, but it gives me the same error again.
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[ SHA1: 58:EA:40:73:F8:0E:7F:07:A7:0B:C3:EE:FB:FA:22:50:18:CF:53:4E ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 6F:12:B6:7B:7F:55:8C:F9:98:B3:78:41:8A:9E:EB:E6:99:7B:91:45 ]
I used same keystore file and password.
Please help me i am new in android developing. Thanks in ad=vance
Please make sure you have used the same Key alias as well. I faced the same error when changed Key alias to a new one.
this solution works for me (but you should find your original keystore)
Download your orginal apk from play store
Deplace your apk to java\jdk...\bin
Open cmd windows and move to the directory with where your file apk
Execute this comand "keytool -list-printcert -jarfile yourfile.apk"
this command will return all infrmation about your file apk
(keystore and password)
Find your keystore (.jks)
Generate your new apk from your keystore
by mistake I was generating in debug and uploading it so make sure you are uploading release type from build.gradle !
I am getting below error from Play Store while uploading new version to existing app.
Upload failed You uploaded an APK that is signed with a different
certificate to your previous APKs. You must use the same certificate.
Your existing APKs are signed with the certificate(s) with
fingerprint(s): [ SHA1:
5D:BC:1C:3E:7A:9E:16:7C:C9:1A:95:2E:82:7F:62:2F:F8:C7:87:D7 ] and the
certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 24:75:9A:E9:A0:D8:AA:C9:EA:71:79:16:CB:08:9D:8C:2E:41:45:05 ]
Since, I formatted my PC after my first version submit. So SHA1 key changed now.
Can you please help to fix this issue?
Thanks
When you format your PC, your debug keystore with new android studio is changed. To upload your APK file to play store, you need a release keystore that you used previously.
Sorry to say - but if you loose the certificate you had before you lost possibility to update this particular application. All you can do is to change application package and to place it as new app. Please keep your keystore in safe place in future.
I'm trying to upgrade my app (developed with appinventor 1.0) on google play. I'm using the same keystore but I get the following message (sorry the ignorance, not sure it matters but for security I changed some of the keys below after SHA1:):
Upload failed
Your APK has been signed with multiple certificates. Please only sign it with one certificate and upload it again.
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[ SHA1: A6:D5:E5:66:34:84:B5:31:8E:8F:79:D7:2A:38:B1:54:5E:29:27:22 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: A6:D5:E5:66:34:84:B5:31:8E:8F:79:D7:2A:38:B1:54:5E:29:27:22,
SHA1: 0D:28:AC:88:7C:D8:FD:0C:BA:A7:46:BC:70:7E:EA:37:9F:A1:CC:84 ]
I am using jarsigner and zipalign afterwards. The first part of the SHA1 is reproduced exactly, but there is an extra SHA1 after a comma.
Any clue ?
Probably you are using the same keystore, but not the same certificate. To update your application you need to use the exactly same configuration (keystore and certificate) you used to submit it.
My guess is that there is another signature present in your apk.
Rename .apk file to .zip and remove any signatures present. Then rename back and do jarsign and zipalign.
After I try to upload an updated APK to the play store I get this error:
Upload failed
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[ ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: FB:BC:61:54:B3:26:6C:73:92:68:65:EA:0C:81:69:81:2B:39:21:66 ]
So I have to find a keystore with...no fingerprint. Can I upload an unsigned APK? I haven't updated the app in years, but I'm still using the only keystore I've ever used.
Edit, I downloaded the live app from the play store. I can't figure out how to get a signature fingerprint, but the keystore I'm using expires the exact same minute that the live application does (in 2036) so it's definitely the key I'm trying to use.
you can't upload an unsigned APK on GooglePlay.
[http://developer.android.com/tools/publishing/preparing.html][1]
Maybe your keystore expired. Do you remember the validity period you set when you originally generated it
It must have been some sort of error on Google's end. They fixed the problem on their end after I opened a support ticket.
My APK uploads now with no modification on my part.
this solution works for me (but you should find your original keystore)
1.download your orginal apk from play store
2.deplace your apk to java\jdk...\bin
3.open cmd windows and move to the directory with where your file apk
4.execute this comand keytool -list-printcert -jarfile yourfile.apk this command will return all information about your file apk (keystore and password)
5.find your keystore (.jks)
6.generate your new apk from your keystore