There is no fix and no workaround. Even if Google Play would allow you to upload your APK signed with a different key, Android devices would refuse to install your update because of that mismatch. If you are really sure that you cannot find your old keystore then you have to publish your update as a new app with a different package name.
On Wednesday, October 9, 2013 4:30:39 AM UTC-5, rahul kaushik wrote: > > Hello , > i have lost my old keystore signing file for the older version of > apk,when i try to upload new apk with new keystore signing file i get the > below 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: BD:C5:13:57:EF:75:00:DE:AC:E7:19:21:FE:64:2B:B9:93:CF:90:2A ] > > and the certificate(s) used to sign the APK you uploaded have > fingerprint(s): > > [ SHA1: A4:6D:AC:EE:47:DA:1F:8A:20:E9:64:64:21:40:85:3F:56:03:BA:12 ] > > Please suggest > > Thanks > RK > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
