Test deep links before launch: App Links and Universal Links
· 7 min read
You send a password reset email. The person taps the link. The app should open on the reset screen. Instead the phone opens a browser, or the store, or your app on the home screen. You may never see this on your own phone. This post is a short way to check deep links before launch. I checked the vendor pages in November 2026.
Why deep links fail without a sound
A deep link is a web link that should open a screen inside your app. There are two kinds. A custom scheme looks like myapp://item/42. It is easy to set up, but nothing proves the link belongs to you. A verified web link is an ordinary https link that the phone has checked against a file on your website. Android calls these App Links. Apple calls them universal links.
The failures are quiet: the link opens the browser, the link opens a store page, or the app opens on the wrong screen. Nothing crashes, so no crash report tells you.
Short answer: set up the verification file on your website and the matching setting in your app, check the file in a browser, then tap the real link on real phones, from the apps your users use, with and without the app installed.
Android App Links
Android's page on adding App Links says the android:autoVerify="true" attribute "is required for App Links". It goes on the intent filter in your manifest. The intent filter must include <data> elements for both the http and https schemes, plus the hosts you want verified. The page's example comment says "Do not include other schemes, as this will prevent verification."
The other half is a Digital Asset Links file. Android's page on configuring assetlinks.json says to publish it at https://domain.name/.well-known/assetlinks.json. It uses a package_name and sha256_cert_fingerprints. A minimal file follows the page's example, with my placeholders:
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "com.example",
"sha256_cert_fingerprints": ["YOUR_SHA256_FINGERPRINT"]
}
}]The same page lists what to get right on the server:
- It is served with content-type
application/json, over HTTPS. - It must be accessible "without any redirects (no 301 or 302 redirects)".
One gotcha is the fingerprint. The page says that if you use Play App Signing, "the certificate fingerprint produced by running keytool locally will usually not match the one on users' devices." It says you can check in Play Console under Release > Setup > App signing, where you will also find the correct Digital Asset Links snippet. So do not copy the fingerprint from your local keystore and assume it is right.
Checking verification on Android
Android's page on verifying App Links says that after you install the app, you should "Wait at least 20 seconds for the asynchronous verification process to complete." It gives this command to check whether the system verified your app:
adb shell am start -a android.intent.action.VIEW \
-c android.intent.category.BROWSABLE \
-d "http://domain.name:optional_port"The page also describes a manual check, which it says works "Starting in Android 12". To read the result, run this command:
adb shell pm get-app-links PACKAGE_NAME The page says domains that pass have a domain verification state of verified. Any other state "indicates that the domain verification couldn't be performed".
If you change the file later, the same page says changes "can take up to seven days" to reach all devices on Android 15 and higher. So a server fix may not show on a test phone right away.
iOS Universal Links
Apple's page Supporting associated domains covers both halves. In your app, you add the Associated Domains capability in Xcode. Each domain entry uses the format <service>:<fully qualified domain>, and the entitlement page says the applinks service is for universal links. So an entry looks like applinks:example.com. If your site uses several subdomains, the page says each needs its own entry "and each must serve its own apple-app-site-association file."
On your website, you create a file named apple-app-site-association "(without an extension)". It lists your app identifiers in the applinks service, in the format <Application Identifier Prefix>.<Bundle Identifier>. Apple says the URL should match https://<fully qualified domain>/.well-known/apple-app-site-association, and adds: "You must host the file using https:// with a valid certificate and with no redirects." The page I read does not state a content type for the file, so I will not guess one.
There is also a delay to know about. The same page says that on macOS 11 and iOS 14 and later, apps no longer ask your server directly. They ask "an Apple-managed content delivery network (CDN)". It says the CDN requests your file "within 24 hours" and that "Devices check for updates approximately once per week after app installation." If you fix the file, a phone may not notice the same day.
Testing on iOS
I did not find step-by-step test instructions on the Apple pages I read. They do document one development aid. On the associated domains entitlement page, adding ?mode=developer to the entry means "only devices in developer mode can access the domain." That is for development builds. For a real launch check, install a build the way your users will get it, and tap real links on real phones.
Apple's page on linking apps and websites to your content says: "If the person hasn't installed your app, the system opens the URL in their default web browser, allowing your website to handle it." So the web page behind the link matters too.
Hosting gotchas
Both vendors say no redirects. Many single-page app hosts rewrite every path to index.html, so a request for /.well-known/assetlinks.json can come back as your app's HTML page with a 200 status. I can't say how every host behaves, so check yours. Open the file's URL in a browser. Then run curl -i https://your-domain/.well-known/assetlinks.json and read the status line and content-type header. You want a 200, no redirect, and JSON, not your home page. Do the same for apple-app-site-association.
Where links get opened from
Your users tap links in an email app, a chat app, a social app, a notes app, and sometimes a browser inside another app. Apple's page says that tapping a universal link in Safari on the same domain opens it in Safari. I did not read what other apps do, and I won't guess. Test it, don't assume. Send the link to yourself and to a friend through the apps your users use, and tap it in each one.
What testers should check
- App installed: tap the link. Does the app open on the right screen, not the home screen?
- App not installed: tap the link. Is the web page or store page sensible?
- Signed out: tap a link to something that needs a login. Do they sign in and then land on the right screen, or land on the home screen?
- From an email and from a chat app: does it behave the same in both?
Here is task text you can paste. Change the link: "Tap this link in your email app: (link). Tell me if my app opened, and which screen you saw. Then paste the same link into a chat app and tap it there. Tell me your phone and OS version, and whether the app was installed." For more on wording, see how to write a test task.
Getting builds to testers: see TestFlight public links and Firebase App Distribution.
Where TestSwap fits
TestSwap is a free app testing exchange. It is not affiliated with Apple or Google, and it does not replace the checks above. It gives you testers on other phones, who can tell you where a link landed.
- Makers post web, iOS and Android apps with a link testers can open or install, like a TestFlight link or a Google Play testing link.
- You can add a test login that only signed-in testers see.
- Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1.
- The maker can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.
I can't promise how many testers or reviews your app will get. Put the deep link and the paste-ready task in your test task, and ask testers to say which screen they saw.
The deep link checklist
- Does the Android intent filter have
android:autoVerify="true"and both http and https schemes? - Is
assetlinks.jsonat/.well-known/, served as JSON over HTTPS, with no redirect? - If you use Play App Signing, did you take the fingerprint from Play Console?
- Does
adb shell pm get-app-links PACKAGE_NAMEshowverifiedfor your domain? - Does the Associated Domains entry say
applinks:plus your domain? - Is
apple-app-site-associationat/.well-known/, over HTTPS with a valid certificate, no redirect? - Did you check both files with curl, and not just in your own browser?
- Did you tap the link with the app installed, not installed and signed out?
- Did you tap it from an email app and a chat app, on both platforms?
Try it
Open both verification files with curl today, then tap one real link on your own phone from your email app. Fix what you see. Then post your app on TestSwap with the deep link in your test task, and review someone else's app first to see how it works. Tell me what's missing or broken (@dizid on X).