Hi Guys
Just picked up and old project (last released in Feb 2018). fixed some warnings (SDK version etc), then recompiled it (using the current keystore) and attempted to release it to the Google Pay as an update.
When I uploaded the apk file I got the following error
------
You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:SHA1: 61
and the certificate used to sign the APK that you uploaded has fingerprint:SHA1: 02:FB:F2:C2:0F:52:C7:AC:AD:48:EA:95:BC:AB:9E:08:82:51:84:00
------
This suggests to me that I am using the wrong keystore file.
I believe, back in 2018 another keystore was used - found the file but no-one can remember the password!
Question - Google Pay App Signing has been enabled - is it possible to change to the current Keystore file on an already released App.
Kind regards
Dave Morris
Just picked up and old project (last released in Feb 2018). fixed some warnings (SDK version etc), then recompiled it (using the current keystore) and attempted to release it to the Google Pay as an update.
When I uploaded the apk file I got the following error
------
You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:SHA1: 61
and the certificate used to sign the APK that you uploaded has fingerprint:SHA1: 02:FB:F2:C2:0F:52:C7:AC:AD:48:EA:95:BC:AB:9E:08:82:51:84:00
------
This suggests to me that I am using the wrong keystore file.
I believe, back in 2018 another keystore was used - found the file but no-one can remember the password!
Question - Google Pay App Signing has been enabled - is it possible to change to the current Keystore file on an already released App.
Kind regards
Dave Morris