Deep linking
What is an app signing certificate fingerprint?
Short answer
An app signing fingerprint is the SHA-256 hash of the certificate that signs an Android app, written as 32 pairs of hexadecimal characters separated by colons. Android uses it to identify exactly which build may act for a domain, which is why assetlinks.json lists it next to the package name.
What it identifies
Every Android app is signed with a certificate before it can be installed. The fingerprint is a short, fixed-length summary of that certificate. Two builds signed with the same key have the same fingerprint, and a build signed with any other key doesn’t.
For Android App Links this is the proof of identity. The package name alone could be copied by anyone. The package name together with the fingerprint, published in assetlinks.json on your domain, tells Android that this particular signed app is allowed to open your links. The field takes a list, so one file can cover several keys.
The Play App Signing trap
With Play App Signing there are two keys. You sign what you upload with an upload key. Google Play then signs the app that reaches people’s phones with the app signing key it holds. The two keys have different fingerprints.
This is the most common reason App Links fail in production while working in testing. Android’s documentation states it plainly: if you use Play App Signing, the fingerprint you get by running keytool locally will usually not match the one on users’ devices. A debug build is signed with yet another key. If the file lists only the fingerprint from your own machine, the Play build never verifies and links open in the browser.
Where to find the right one
For the Play build, open the app signing page in Play Console. It shows the app signing key certificate with its SHA-256 fingerprint, and, according to Android’s documentation, a ready Digital Asset Links snippet for the app. Copy every fingerprint listed for the app signing key.
For a key you hold yourself, run keytool -list -v -keystore followed by the keystore file and read the SHA256 line. To see what is actually installed on a test phone, adb shell pm get-app-links with the package name prints the app’s signatures next to the verification state of each domain. Put the Play fingerprint in the file first, then add the upload or debug fingerprint if you also want links to open in test builds.
14:6D:E9:83:C5:73:06:50:D8:EE:B9:95:2F:34:FC:64:16:A0:83:42:E6:1D:BE:A8:8A:04:96:B2:3F:CF:44:E5Try it here
Generate the file for your app
Enter your Team ID and bundle ID, or your package name and signing fingerprint. You get an apple-app-site-association or assetlinks.json file ready to put on your server.
Apps
Add every app that should open links on this domain. Each one becomes an entry in appIDs.
- App 1
10 characters, in your Apple Developer account under Membership details.
From your app target in Xcode, for example com.example.app.
Paths that open the app
Rules are checked from top to bottom and the first match wins, so put exclusions above broader rules. * matches any characters, ? exactly one.
- Rule 1
name=value pairs joined by &
Other services
Your file
apple-app-site-association
Example. Fill in your details to replace it.
{
"applinks": {
"details": [
{
"appIDs": [
"ABCDE12345.com.example.app"
],
"components": [
{
"/": "/*"
}
]
}
]
}
}Generated in your browser. Nothing is sent anywhere.
Where to host it
Where the file goes
- Upload it to
https://your-domain/.well-known/apple-app-site-association, without a.jsonextension. - Serve it over HTTPS with a valid certificate and a direct 200, with no redirects.
- Send the header
Content-Type: application/json. - Repeat on every host in your links:
example.comandwww.example.comeach need the file and anapplinks:entry. - Apple’s CDN fetches a new file within 24 hours. Test with
?mode=developerin the meantime.
Rather not host files yourself? Smart links are free, and on Enterprise Appy serves both files on your app’s link domain.
Create a free linkFrequently asked questions
Where do I find my app’s SHA-256 fingerprint?
For the build people download from Google Play, on the app signing page in Play Console, under the app signing key certificate. For a keystore on your own machine, run keytool -list -v -keystore with the keystore file. The two values differ when Play App Signing is on.
What is the difference between the upload key and the app signing key?
The upload key is yours. You use it to sign the bundle you send to Play Console. The app signing key is held by Google Play and signs the app that is delivered to devices. Android checks links against the delivered app, so assetlinks.json needs the app signing key’s fingerprint.
Can assetlinks.json contain more than one fingerprint?
Yes. sha256_cert_fingerprints is an array, and Android’s documentation says multiple fingerprints can support different versions of the app, such as debug and production builds. Listing the Play app signing key and your debug key lets links open in both.
Related terms
- assetlinks.json
assetlinks.json is the Digital Asset Links file that proves to Android your domain trusts your app, so verified App Links open the app directly. It sits at /.well-known/assetlinks.json, is served over HTTPS as JSON without redirects, and lists your package name with the SHA-256 fingerprints of your signing certificates.
- Android App Links
Android App Links are https links that Android has verified as belonging to your app, so a tap opens the app directly instead of asking which app to use. They work on Android 6 and later on devices with Google services, and need an intent filter with autoVerify plus an assetlinks.json file on your domain.
- Bundle ID
A bundle ID is the unique string that identifies an iOS app, such as com.example.app. Android’s equivalent is the application ID, usually called the package name. You choose both, they normally follow reverse-domain style, and neither should change after the app is published. Google Play links and assetlinks.json use the package name.
One link for every phone
Create a free smart link and QR code that sends iPhones to the App Store, Android phones to Google Play and desktops to your website.