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.
Related
I had developed my app in xamarin forms and release my android app with playstore. and unfortunately I have to change my system. Now I have done some changes in app and I want to release that new apk in playstore then I am getting this given below:
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: 70:9A:CF:42:5E:98:B9:4D:B2:F6:B7:2E:AC:C4:64:14:4B:5D:76:18 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 62:E0:24:5F:18:95:47:95:60:C3:08:B2:D5:16:E8:C5:46:D1:D7:4E ]
Please help me as I am new with xamarin forms development
Thank you
The apk you uploaded first time(the apk which is live on playstore), had a different signing key compared to the apk you are trying to upload right now.
Once an apk is uploaded on the store, you always have to use the same applicationId and signing key as you used for the first time uploading. If your ever loose your key, you can never update the same apk again.
Edit:
Starting from May 2017, there is an option to upload your keys and back them up in google servers. But you have to opt in to this service. They will backup they keys you uploaded and give them back when you need them. But if you don't opt in for this service already, before losing your keys. you are out of luck
I think you are using different keystore singing file from your previous version keystore file. Please make sure use the same file every time when you are creating signed api for google play store upload.
Keystore file is generated when we create signed apk first time for upload to play store. This file is with extension .jks
References
https://developer.android.com/studio/publish/app-signing
https://headjack.io/tutorial/create-android-keystore-file/
What is Android keystore file, and what is it used for?
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.
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.
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 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.