One of our apps was being signed outside the Play Store, so in the URL
play.google.com/console/u/6/developers/android-developer-verification
clicking the arrow against that app, it asks us to add the public key.
To find the public key,
where I'm using this method in a github action,
- name: Extract SHA-256 fingerprint only
run: |
BUILD_TOOLS="$ANDROID_HOME/build-tools/34.0.0"
"$BUILD_TOOLS/apksigner" verify --print-certs app-release.apk \
| grep -i "SHA-256"
I clicked on Add Key and added the digest, at first it showed Pending verification, in 10 minutes it showed verified.
Here is part of Gemini's reply on why this key is needed -
To ensure your app functions flawlessly whether it is downloaded from the Play Store, sideloaded by a QA tester, or downloaded directly from your website, your backend services (Firebase, Google Cloud, etc.) should always have both fingerprints registered:
- The Google Play App Signing SHA-256 (found in Play Console -> Release > Setup > App Integrity).
- Your Local Keystore SHA-256 (the one generated from yourkey.keystore).
No comments:
Post a Comment