Google Play Console - The private key doesn't match the current app certificate

Question

I am trying to upload a bundle to I can do Closed Testing with app on my own devices. When I try to upload I am told that I need to opt-in to "Play App Signing":

When I try to upload a private key under App integrity I am being told "The private key doesn't match the current app certificate"

How do I fix this? I don't know where the "current app certificate" is or how I would generate/upload a new certificate.

Answer 1

I know I am too late to answer this, but this might help other users. I faced exactly same issue, So the issue was I was using wrong keystore file. I was having two keystore files, but only one is correct, If you have multiple files, and not sure about they are same or different, Just check those using command

keytool -list -v -keystore foo.jks -alias foo

Change file path and alias and check sha keys if they are different please retry to create pem file, with other keystore. Thanks happy coding

Answer 2

The only way I could fix this problem was to rebuild the app with completely different package names. So I changed com.myapps.thisapp to com.myapps.thisapp2 and I was able to upload.

I guess whatever keys/certificates that were on my machine from 8 years ago were needed to upload a newer version of my app.