Develop Reference

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.

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.

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.

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.