Android App Links Verification
Android App Links allow your app to become the default handler for a specific website’s URLs. This requires proper verification of your domain ownership.Step 1: Create the Digital Asset Links JSON File
Create a file namedassetlinks.json
with the following content:your.package.name
with your actual Android package nameSHA-256:XX:XX:XX:...
with your app’s SHA-256 fingerprint
Step 2: Get Your App’s SHA-256 Fingerprint
To obtain your app’s SHA-256 fingerprint:-
For debug builds, use:
-
For release builds, use your release keystore:
- Look for the “SHA-256 Certificate fingerprint” line in the output
Setting Up Verification with Linkrunner
Linkrunner provides a simplified way to manage your domain verification files through the project settings dashboard.Step 1: Access Domain Verification in Linkrunner
- Log in to your Linkrunner dashboard
- Go to “Project settings” from the navigation menu
Step 2: Configure Your Verification Objects
-
Prepare your verification JSON objects:
- For iOS: Create the apple-app-site-association JSON content
- For Android: Create the assetlinks.json content
-
In the Domain Verification section:
- Paste your iOS JSON in the “iOS (Only JSON allowed)” text area
- Paste your Android JSON in the “Android (Only JSON allowed)” text area
- iOS:
https://your-domain.io/.well-known/apple-app-site-association
- Android:
https://your-domain.io/.well-known/assetlinks.json
- Click the “Save” button to store your configuration
Step 3: Verify Your App Configuration
After configuring in Linkrunner, you need to:- For iOS: Ensure your app has the Associated Domains capability with
applinks:your-domain.io
in Xcode - For Android: Verify your app’s intent filters are properly configured for App Links
Testing Deep Link Verification for Android
- Install the app on a device
- Open a link to your verified domain in a browser
- The app should open automatically without prompting
adb
to test:Troubleshooting for Android
-
App doesn’t open automatically:
- Ensure your
assetlinks.json
file is correctly formatted - Verify the SHA-256 fingerprint matches your app signing key
- Make sure the file is accessible via HTTPS
- Ensure your
-
Verification warnings in logcat:
- Look for “IntentFilterIntentSvc” messages in logcat for details on verification failures