Apk not upload in google playstore - android

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?

Related

You uploaded an APK that is not signed with the upload certificate with same keystore

im using flutter, after i formatted my pc when i want to build and upload apk file to the play store show me bellow, error by the way i have project with same keystore
You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:
[ SHA1: ]
and the certificate used to sign the APK you uploaded have fingerprint:
[ SHA1: ]
Try downloading this software (GUI) https://keystore-explorer.org/ . I saw with this tool that my Keystore had diferent certificates and aliases. So I could compare which one Google Play was asking for. Then I could sign with the correct alias and upload an update of my app.
Well it seems like you are trying to upload an update of your app or trying to sign apk with different security certificate than the previous version.
For more details check Android Developers Guide for signing APK
When you have formatted, have you kept a copy of the keystore (*.jks or *.keystore file)? You should sign your APK (or App Bundle) using the same one you used to upload the first versions of your app to Google Play Console.
If you have lost that keystore file, since it looks like you are enrolled in Google Play Signing, you can request your upload key to be reset by contacting the Developer Support directly: see "Create a new upload key" at https://support.google.com/googleplay/android-developer/answer/7384423"

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.

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.

apk with different certificate

I'm facing a problem with the certificates, two weeks ago I made a backup of my pc, I save the project and the key.jks now in a different computer I'm trying to upgrade my app but It says 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: 90:F7:82:F9:C0:52:98:D7:EA:F9:9C:79:B9:00:1D:61:7E:5B:C5:06 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 7B:67:D7:7B:C6:EB:53:49:94:41:86:89:C0:7A:2B:89:5B:0B:AC:A8 ]
Is there a way that I can fix this problem, the app has active users and I don't want to loose them
You cannot update your Apps, if you lost your APK Key. That is said also on Google's official Guide, to why it is soo important to save your API Keys.
You could try and contact Google Play service, but I doubt you'd get a positive respond or any respond at all. Best is to delete the App and re-create it and post it.
Otherwise, you can leave it there and you won't be able to update it without the original Key.
Here from official site Signing Your Application:
Warning: Keep your keystore and private key in a safe and secure
place, and ensure that you have secure backups of them. If you publish
an app to Google Play and then lose the key with which you signed your
app, you will not be able to publish any updates to your app, since
you must always sign all versions of your app with the same key.

Android Play Store App Update

I lost my android apk certificate . Now i want to upload my new apk to the same application again, but its not letting me update and gives me a certificate error
is there a way to extract the certificate from it back ? i have the original apk if its possible using that
the app was build using adobe flash
please tell any details
You need to use a different version code for your APK because you already have one with version code 1000000.
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: 2C:AB:E2:C0:DC:F9:2C:C8:DE:1B:60:DE:84:A1:71:CA:B6:6D:70:8D
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
SHA1: CC:FF:DE:87:AC:5A:08:E5:ED:21:A6:52:1E:56:73:F1:CD:DF:7D:85
thank you
If you have your old keystore then its possible otherwise not. You need to create new application with new package name for this and then you can upload. You must keep your keystore for your application.
You're out of luck. How did you lose that certificate? Can't you do some hard disk recovery? Didn't you do a back up of it some place?

Categories

Resources