I am trying to update a current app on Google Play. I am using a .keystore file that I am certain is the same one as the previous version and I am certain the password is correct. I have updated the versionCode and versionName in the manifest.xml and read through all of the android documentation for submitting an update. I just used this same .keystore to update another app and it worked fine.When I try to upload the new .apk file I get 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: CB:17:93:81:FA:07:6E:B7:4C:83:EA:64:79:85:44:3B:7D:08:71:6E ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: ED:79:37:8A:77:3A:6E:82:8A:60:55:95:99:0E:56:60:CB:5B:3C:EF,
SHA1: CB:17:93:81:FA:07:6E:B7:4C:83:EA:64:79:85:44:3B:7D:08:71:6E ]
as you can see, the 2nd (new) certificate's 2nd SHA1 argument is identical as the 1st certificates. But, for some reason the 2nd certificate has 2 SHA1: arguments. Does anyone know why it would have 2? I cant find any information on this, any help is greatly appreciated.
I only had a quick look but according to this Can we load multiple Certificates & Keys in a Key Store? it is possible to have more than one key, are you sure you used the correct alias?
Related
at my work they have an app which they made using appypie
so now we create a native app so for me I create the android app and now I tried to update the existing one with new apk
so I made the package name , vertion name and vertion code.. ets. everything compatible but google play now refuse the app only because of this reason:
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:
55:A4:8E:1A:17:A0:67:C7:FB:22:EF:B3:63:95:58:EA:C0:FC:31:3F ] and the
certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 03:95:F7:78:3A:6F:1C:0F:A8:4C:57:05:36:9B:F4:C4:10:A2:AE:C6 ]
after contact the appypie they give us the keystore alias name and keystore Password so I create new jks file with same alias and password then build the apk with it
but google still give me the same error of certificate so I contact them and they give me a binary file and told me to get the .jks file from it
so how can do this?
or if there are another solutions for this problem so help me please
You created a new jks file. Don't do that. You need to use the same jks file, not a new jks with the same alias. If you use a new jks file, you have a different signing key.
If you don't have the original jks file, if you have Google App Signing on, you can just contact Google about the new key. If you don't, you're in for pain- google can reset your app to use a new key, but nobody who previously downloaded your app will be able to upgrade without uninstalling.
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: F2:6B:9A:EB:3B:8D:F8:53:59:C7:D3:7D:1D:BC:60:2A:53:28:7C:95 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 82:AC:A8:E7:01:7F:E0:D2:56:DC:8A:98:FB:02:AF:FA:B9:AA:29:4F ]
My Previous app is not hybird app.. now i want to replace .. any solution ?
Using same package name
You must sign the package with the same key, as the previous .apk was signed. You can't change key between versions, the initial signing key for particular package name is final till the lifespan of app.
If you lost the original key (or if your key did expire ... which will eventually happen to most of the apps in 30-50 years), you have to re-release the application under different package name, and build up the user base again.
See official docs for more details:
https://developer.android.com/studio/publish/app-signing.html
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.
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.