How to get the SHA-256 fingerprint
Obtain SHA-256 fingerprints for debug and release signing certificates.
Grovs lists your signing certificate's SHA-256 fingerprint in assetlinks.json, so Android can verify App Links.
Add both your debug and release fingerprints to the Grovs dashboard. Deep linking fails in any build variant whose fingerprint is missing.
Debug fingerprint
In Android Studio, click the Gradle tab on the right.
Open YourApp → Tasks → android and double-click signingReport.
In the Run tab, copy the SHA-256 line under the debug variant:
Variant: debug
Config: debug
Store: /path/to/your/debug.keystore
Alias: your_alias
SHA-256: 12:34:56:78:90:AB:CD:EF:12:34:...cd /path/to/your/project# macOS / Linux
./gradlew signingReport
# Windows
gradlew signingReportCopy the SHA-256 line under the debug variant:
Variant: debug
Config: debug
Store: /path/to/your/debug.keystore
Alias: your_alias
SHA-256: 12:34:56:78:90:AB:CD:EF:12:34:...Release fingerprint
keytool -list -v \
-keystore /path/to/your/release.keystore \
-alias your_alias_name \
-storepass your_keystore_password \
-keypass your_key_passwordIf keytool isn't found, add the JDK bin directory to your PATH.
Copy the SHA-256 value into your Grovs dashboard.
Sign in to the Google Play Console and select your app.
Go to Setup → App integrity.
Copy the SHA-256 under App signing key certificate into your Grovs dashboard. Google re-signs Play Store installs with this key, so your upload key's fingerprint isn't enough.