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.
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.
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.
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.
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.