Develop Reference

Upload Failed n google play store

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.

My SHA1 key changes after formatting my PC. I am unable to submit new version to play store

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.

Converting my application from titanium to ionic and upload to store

I have an application that was originally built in titanium and I have now update the app in ionic platform. The problem is that when I try to upload my update on google play store I get this error:
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: CC:E3:7F:08:FA:03:9C:88:07:BC:CB:AB:7B:88:61:F4:75:9D:47:9F ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 20:9F:16:C0:05:AC:8E:04:C8:B0:D9:A7:AA:40:17:46:FB:1B:1F:7B],
[ SHA1: BB:D7:DC:34:B9:03:73:EA:40:C4:42:B2:01:17:05:EB:75:14:40:4D ]
Google Play Store

This happens because you're signing the new Apk with a keystore different than the one used to sign the old Apps. To solve this you need to sign your Apk with the same keystore used before.

App signed with multiple certificates rejected

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.

Can I replace an unsigned apk with a signed apk in Google Play

I have an app in Google play that I built in Eclipse.
Recently I imported it to Android Studio, made some changes and I want to replace the apk file in the market.
In Eclipse I used unsigned apk and now it's signed one.
Do you know if it can cause problems for the users?
EDIT:
When I try to upload it, this is what I get:
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: 07:F5:24:81:59:0B:28:48:A6:48:FC:E3:9B:D5:3D:06 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 79:B7:5D:76:80:32:22:E4:1B:33:5A:69:69:24:79:BA ]
Does anyone know what should I do?

The first APK you uploaded was most likely signed with a debug certificate as opposed to your release one. Google Play doesn't allow you to use a different certificate than the one you originally used, due to security issues. The whole idea behind the certificates is to prevent anyone from uploading potentially malicious code that claims it was by you, thus keeping you users a little safer. So, the only way to change your certificate is to unpublish your old app, create a new one in the console and re-upload. You will also have to change your app's package name to something else before you re-upload.