我从ADT切换到Android Studio：您将使用其他证书签名的APK上传到了以前的APK

Question

Please read before you post as a duplicate! I am using the same certificate, the only one I have used for years on multiple apps. I have run keytool on the jks I am using and the SHA1 key is the same as Google Play says was used to sign the last accepted apk. I have also run jarsigner on both the new apk and the last accepted one, and they show the exact same certificate information, dates, etc. The only change is I switched from ADT to Android Studio, and I can still upload using ADT using the same cert. And, for the record, the SHA that Google Play says I signed the new apk with is not my debug SHA either. Any ideas? I really don't want to go back to ADT!

Answer 1

This thing is when you first installed your app (from ADT) into your emulator or android device, it was made from ADT, but now you are trying to install the same app, from Android Studio, that is why you are getting this error : You uploaded an APK that is signed with a different certificate to your previous APKs

What you have to do is, first uninstall the previous version of your app from your device (which was installed when using ADT)... And then install the latest APK, by using Android Studio.

You dont have to go back to ADT. Keep using Android Studio, as it is the official IDE for Android Developement.

Edit: For Google Play i am not sure what can be the solution, as i dont know if u can delete an old signed APK and add a new one signed by the same certificate... Switching from ADT to Studio usually gives these kind of problems.