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?
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?
at my work they have an app which they made using appypie
so now we create a native app so for me I create the android app and now I tried to update the existing one with new apk
so I made the package name , vertion name and vertion code.. ets. everything compatible but google play now refuse the app only because of this reason:
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:
55:A4:8E:1A:17:A0:67:C7:FB:22:EF:B3:63:95:58:EA:C0:FC:31:3F ] and the
certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 03:95:F7:78:3A:6F:1C:0F:A8:4C:57:05:36:9B:F4:C4:10:A2:AE:C6 ]
after contact the appypie they give us the keystore alias name and keystore Password so I create new jks file with same alias and password then build the apk with it
but google still give me the same error of certificate so I contact them and they give me a binary file and told me to get the .jks file from it
so how can do this?
or if there are another solutions for this problem so help me please
You created a new jks file. Don't do that. You need to use the same jks file, not a new jks with the same alias. If you use a new jks file, you have a different signing key.
If you don't have the original jks file, if you have Google App Signing on, you can just contact Google about the new key. If you don't, you're in for pain- google can reset your app to use a new key, but nobody who previously downloaded your app will be able to upgrade without uninstalling.
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.
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.