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.

Uploading signed apk on playstore

When i am going to upload the updated signed apk of my app then it gives me error i.e."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): "
What should i do in this case?

This error is accruing because you have used another keystore for the new version of the app while the older version was signed with another key store.
In order to give update to your apps you must sign your app with same key store when generating signed APK, otherwise you can't give update.

Package app with proper keystore certificate [duplicate]

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.

How to update an .apk that contains two SHA1 fingerprints?

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.

apk upload issue [duplicate]

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.