This question already has an answer here:
Upload fail with APK with 2 certificates entries that are valid
(1 answer)
Closed 6 years ago.
I am trying to update my app in Google Developer, but receive the 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: AF:AF:68:1E:2B:5C:99:23:4D:B9:87:F6:D6:2F:9D:5A:9A:BE:34:EC ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1:2A:84:1D:BC:91:68:55:B1:F3:90:47:FB:3B:56:29:21:F2:38:4A:37 ]
However, using keytool, the keystore file contains 2 entries, both of these certificates.
How do I package the app using the correct keystore certificate that matches so I can submit an upgrade?
You have to use same keystore file and same alias as used before. So it is always better to make a backup of the kestore file alias and password in cloud when you publish an app.
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.
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.
This question already has answers here:
Lost my keystore for uploaded app on android market [duplicate]
(2 answers)
Closed 9 years ago.
I want to update my app in the Google Play but this message opened.
I deleted my keystore.
What I can do for update the apk?
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: 30:36:E4:D2:CE:4F:3A:C9:66:93:EF:BB:67:B0:77:7A:6A:78:57:B6 ]
and the certificate(s) used to sign the APK you uploaded have
fingerprint(s): [ SHA1:
0F:91:AD:5A:76:D5:99:E5:F2:97:82:58:BA:16:18:75:A9:92:01:BB ]
There is nothing you can do unfortunately. Maybe you could try doing a system restore, on your computer, to a previous date in which you haven't misplaced or deleted your key yet.
This question already has an answer here:
Can't upload updated APK to Google Play due to different certificate [duplicate]
(1 answer)
Closed 8 years ago.
After i finished "export signed application package" for my android application, i want to upload my last version application to google play.
I get error message like this :
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: FC:DA:7B:3C:33:A2:87:41:D6:25:8C:FB:81:BD:07:62:37:16:CA:95
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
SHA1: 34:BF:77:B0:49:FF:BB:6F:FA:29:49:90:F4:70:0A:94:74:45:15:A8
how to fix this error?
Thank you
*The Apk Must be Signed with the Same old Certificate,
But Now u Are signing With New Certification*
You have to make sure that the original APK you uploaded is signed with the same certificate. Else you have to upload the file as a new package (new app).
The apk must be signed with the same old certificate, if you have a backup of it, try to sign the apk withe old one. If you don't have old certificate then there's no way.
This question already has an answer here:
Can't upload updated APK to Google Play due to different certificate [duplicate]
(1 answer)
Closed 8 years ago.
I published a application in android market, now I try to upload a updated apk (version code, version name T already changed)
it gives a error that
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:
82:FE:C4:DA:82:B3:20:2A:84:9F:26:E4:5D:6A:AF:0A:CA:91:1D:5A and the
certificate(s) used to sign the APK you uploaded have fingerprint(s):
SHA1: D2:B1:C5:7A:8A:1A:5B:FE:8C:EF:4E:3A:22:58:16:0B:89:6A:B0:AF
i need to update very soon, is anyone faced this problem or
how to resolve it.
You need to keep your keystore and your keys consistent, otherwise the Play Store will not accept your updated app for the same store listing.
You can check your debug keystore in eclipse Windows-> preferences->Android->build. Here you can check the keystore path. If both the app have different key store the change the new app key store to old one.It will solve the issue.