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.
Related
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 answers here:
I lost my .keystore file?
(12 answers)
Lost my keystore for uploaded app on android market [duplicate]
(2 answers)
Closed 8 years ago.
I'm generating a signed APK from Android studio. However, for some reason I can't seem to use the keystone I used previously. Android studio keeps complaining "Keystore was tampered with or password was incorrect". I believe the password is correct.
Anyways, I created a new keystone and generated my signed APK. However, when I try to upload this APK in Beta Testing by clicking on button Upload new APK to Beta I get an 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):
Question
How can I upload a new APK to my Beta with a different certificate? Or Is there a way to reset password for my .jks file?
My goal is to simply push a new beta version out.
Quick answer: You can't.
Without the certificate you can't upgrade an app, making it's package also "locked" in the last APK you've uploaded.
Now.. you either manage to find the correct password (assuming you're using a wrong one and that's the problem) or.. you'll have to change the app to a new package name, and warn you're users on the description of the old app or something like that...
Several people had the same problem before:
Lost my keystore for uploaded app on android market
Retrieve Private Key for Existing Android App
...
You can't upload the new APK to beta. You need to use the same keystore file as you did for the original app. My guess is your password is wrong, based on the error message you're getting. I would try some the keystore password crackers out there to see if you've got a close password.
An interim fix would be to change the package name on the application, and upload it as a new one to beta, but you can't make any updates to your existing app if you don't have the correct keystore/password combo.
This question already has answers here:
The apk must be signed with the same certificates as the previous version
(15 answers)
Closed 9 years ago.
I have an existing app that has been on the market for over a year and has been through many upgrades. Recently I changed the way I built my app, making it into a library so that it would be easier to make multiple variations of the app - free/paid/alternative markets etc. etc. Now I've made some graphical changes so wish to update my standard version that is on google play, but upon uploading I get the following message:
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: E5:FC:E7:30:F4:B2:91:16:94:3B:31:6D:B0:CA:FA:D4:A1:D8:5E:12 ]
So it looks like my current apk has no fingerprint (whatever that is) at all. How could that be?
EDIT: I have seen similar questions on SO, but the answers either did not apply, or I didn't understand how to implement the solutions.
EDIT: I have just found a backup of my original keystore file and used that when exporting my project. But google gave exactly the same error. So to recap, I have my original keystore file, I used the same alias, the same pair of passwords... and still have the same error.
From documentation:
Before uploading the updated application, be sure that you have incremented the android:versionCode and android:versionName attributes in the element of the manifest file. Also, the package name must be the same and the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update.
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.