Can't upload updated APK to Google Play due to different certificate Upload failed You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint: [ SHA1: 65:88:94.7:24.F:C3:F6:BC:F1:3F:B9:30:FC:28:5F:C7.7:E5:71 ] and the certificate used to sign the APK you uploaded have fingerprint: [ SHA1: 40:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:** ] When I upload my APK to Google Play, it keeps showing me this error in spite of using the same keystore which I used for earlier versions of my game. Can anyone know the solution to this problem?
Are you sure you used the exact same keystore file as the one before? @RishabhMehta . This happened to me. turns out I used a test keystore file. BTW. There's a process here suggested by Google for resigning the app https://support.google.com/googleplay/android-developer/answer/7384423
I am sure you are using the wrong keystore file, it happens a lot, search in your folders, maybe you forgot it somewhere.
Which file are you talking about? Is it .jks file I know my keystore password & alias but still I don’t why I am getting errors
Yes I am talking about the .jks file, developer console wouldn't give you the error if you are choosing the right .jks, obviously it's the wrong one, that's what happened with me once, and then I started all over and signed it with the right .jks file.
One thing I want to clear is how the SHA1 certificate number will change just by selecting old .jks file?
Yes, the keystore file is the .JKS file. Even if you create a new keystore with the same alias and password, it won't work anymore because it will still be a different .JKS file with a new SHA number. Do what you can recovering the old one. And always backup and safekeep a keystore for it will always be needed. It's impossible for me to make a video about it. But I think there are lots of articles online about this topic that would do a lot better in terms of explaining, and they are more of an authority on the subject. Good luck!
Just like Darius said, the SHA will be different, so if you sign it with same alias and password it will not work, I read on some websites that you can get the keystore back, but I am not sure honestly, but you can try and contact google and tell them what happened.
