APKS cerificate whith fingerprints? - android

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: 9E:DF:7F:E1:2E:D2:A2:47:2F:B0:7D:F1:E3:98:D1:03:9B:9D:2F:5D ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: DC:38:7D:1A:C0:DF:1A:CF:70:98:0A:28:12:07:55:DE:B7:Hello,F ]
Hello,
I have this problem, I create app whit Seattle could and now this is closed and all my app now no function .... I created a new APK for the android studio, but do I get this error .... how can I solve it?
Thanks

Related

APK that is signed with a different certificate to your previous APKs

I need help in android application created in eclipse which is already live BUT it has some complication so we had recreate this project on Android studio.After complete debug testing, Now client is trying to make the new apk live by upgrading previous live apk. AND while doing this, client getting following 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:
52:D5:6D:B3:88:30:B7:88:3F:4D:8B:D5:37:67:FF:E1:93:7A:E9:89 ] and the
certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: B1:53:ED:20:41:2E:1F:0E:1F:5B:54:F3:8D:44:7C:59:AC:EE:FE:DB
------------------------------------------------------------------------ ].
I googled the solution for this error but not found any proper solution. Can you please guide me for resolving the above error.
The answer is already in error description: "You must use the same certificate". Seems you generate signed apk using different from old version certificate (.jks file)

APK upload certificate error on Google Play Console

I have just finished some very minor bug fixes on our app and have generated a signed APK. I have tried to upload this on Google Play Console to give a release but I get this error. I have used the correct Keystore and application runs fine when tested on a device.
ere is 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: 7D:24:1D:9B:55:33:AC:7D:C6:72:E6:4B:45:83:92:B1:BF:60:3C:D6 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: CB:8F:D6:DD:68:DA:40:3B:D9:46:6D:F4:5C:C1:A5:EB:3B:17:04:93 ]
Any ideas why?
Thank you.

Application Updating Error

I Upload A New Version Android App in Google Play store , But Not successfully , I See Error , That Error is Bellow , Please Help Me ?
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: 27:7C:DC:76:0B:18:AE:F8:30:3A:48:CA:08:9C:6B:23:44:E6:E4:D2 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 1B:93:3C:5E:55:F5:41:15:8D:64:CC:18:48:0C:A8:4D:7B:47:1B:FD ]
You have to use the same keystore to sign your APK that you used to sign in the first time

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.

Google Play: Upload new APK failed. APK is signed with different certificate to previous APK.

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: 33:00:07:BA:2B:DC:9C:29:B0:B9:54:F1:AA:C9:9C:00:6A:D0:93:35 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 60:BB:1D:CA:5F:5A:0B:7C:62:8B:11:CE:88:2D:FC:8F:FA:ED:D6:FD ]
I am using same Key Store to generate signed APK. Previously I generated signed APK from Windows OS but this time from a Linux Ubuntu using SAME key store.
Make sure to use the same File and not just create the "same" certificate by using same login / password / infos to generate it.
Are you sure to use Release key and not debug ?
Open your gradle and double check again your keystore key

Categories

Resources