Expo deep linking: Universal Links and App Links in an Expo app
How to make https links open your Expo app on iPhone and Android: app.json settings, the two files your domain must serve, Expo Router, why Expo Go can't test it, and what an over-the-air update can't change.
· DL2App · 5 min read
An Expo app can open from a custom scheme like myapp://product/42 with almost no setup. The links people actually share are https links, and getting those to open the app takes a few more pieces: settings in app.json, two files on your domain, and a native build that includes them.
This guide covers each piece, the Expo-specific traps, and how to check it works.
The short answer
- Add the domain to
app.json:ios.associatedDomainsand anandroid.intentFiltersentry withautoVerify: true. - Serve two files on that domain:
apple-app-site-associationandassetlinks.json, under/.well-known/. - Make a new native build. These settings are compiled into the app. Expo Go can't use them, and an over-the-air update can't add them.
- With Expo Router, the path picks the screen.
https://go.example.com/products/42opensapp/products/[id].tsx.
1. Settings in app.json
{
"expo": {
"scheme": "myapp",
"ios": {
"bundleIdentifier": "com.example.myapp",
"associatedDomains": ["applinks:go.example.com"]
},
"android": {
"package": "com.example.myapp",
"intentFilters": [
{
"action": "VIEW",
"autoVerify": true,
"data": [{ "scheme": "https", "host": "go.example.com" }],
"category": ["BROWSABLE", "DEFAULT"]
}
]
}
}
}
associatedDomainsbecomes the Associated Domains entitlement on iOS. Add oneapplinks:entry per host, withouthttps://and without a path.intentFiltersbecomes anintent-filterin the Android manifest.autoVerify: trueis what makes Android check your domain and open the app without asking. AddpathPrefixto thedataentry if only some paths should open the app.schemeis optional for https links, but it's useful as a fallback and for development.
2. The two files on your domain
Phones only open your app if the domain agrees. Expo doesn't create these files; whatever hosts the domain must serve them.
iOS: https://go.example.com/.well-known/apple-app-site-association, with status 200, as JSON, and no redirect:
{
"applinks": {
"details": [
{ "appIDs": ["ABCDE12345.com.example.myapp"], "components": [{ "/": "/*" }] }
]
}
}
ABCDE12345 is your Apple Team ID. If you build with EAS, it's the team of the Apple account EAS signs with.
Android: https://go.example.com/.well-known/assetlinks.json:
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "com.example.myapp",
"sha256_cert_fingerprints": ["AB:CD:..."]
}
}]
The fingerprint must match the key that signed the installed app. With EAS, eas credentials shows the upload keystore's SHA-256. If Google Play signs your releases, also add the app signing key from Play Console, under Test and release → App integrity. Builds from Play are signed with that key, not yours. Where to find the Team ID and fingerprints.
Our AASA generator and assetlinks.json generator write both files, and the link checker fetches them the way phones do.
3. Build the app again
The domain settings are part of the native app, so:
- Expo Go won't work. It's a different app with its own bundle ID, and your domain doesn't list it. Use a development build (
npx expo run:ios,npx expo run:android, or an EAS development build). - An over-the-air update can't add them. EAS Update changes JavaScript, not entitlements or the manifest. Users need a new store version before your https links open the app for them.
- If you use prebuild, run
npx expo prebuild --cleanafter changingapp.json, so the native projects pick up the new settings.
4. Handling the link in your code
With Expo Router, incoming links are routed by path. A tap on https://go.example.com/products/42 opens app/products/[id].tsx with id set to 42. Make sure every path you share has a route, or the app opens on a "not found" screen.
If your links don't match your routes (short links like /s/x7k2, or a path you want to rewrite), add app/+native-intent.ts:
export function redirectSystemPath({ path, initial }) {
// Turn /s/x7k2 into a route the app knows, or return path unchanged.
return path;
}
Without Expo Router, read the link with expo-linking:
import * as Linking from "expo-linking";
export default function App() {
const url = Linking.useURL(); // the link that opened the app, then any new ones
// parse url and navigate
}
5. Test it
- iPhone: tap the link in Notes or Messages. A link typed in Safari's address bar never opens an app.
- iOS simulator:
xcrun simctl openurl booted "https://go.example.com/products/42". - Android:
adb shell pm get-app-links com.example.myappshould show your domain asverified. - Inside Instagram and TikTok: links often stay in the app's own browser. Why, and what helps.
If the app doesn't open, our checklists for Universal Links and App Links work through the causes in order. How to test both.
What this doesn't do: links that survive an install
Universal Links and App Links only work when the app is already installed. If someone taps the link without the app, they go to your website, and after installing they land on the home screen with the link forgotten. Carrying the link through the install is deferred deep linking, and Expo doesn't do it on its own. How it works in React Native and Expo.
How DL2App fits
DL2App hosts both files on your link domain, checks them on a schedule, sends each phone to the right store when the app isn't installed, and carries the link through the install. The React Native SDK works with Expo (SDK 51 or newer, in a development build): its config plugin adds the associated domains and intent filters for you, and one listener receives both direct links and the link after an install.
npx expo install @dl2app/react-native
To start, paste your App Store or Google Play link at portal.dl2.app: your first link is live in about a minute. See the React Native and Expo docs and pricing.
Questions people ask
Why doesn't my https link open my app in Expo Go? Expo Go is a separate app with its own bundle ID, and your domain's files list your app, not Expo Go. Test https links in a development build.
Can I add Universal Links with an EAS Update?
No. Associated domains and Android intent filters are native settings. Change app.json, make a new build, and ship it through the stores.
Do I need a custom scheme for deep linking in Expo?
Not for https links. A scheme like myapp:// is handy for development and some integrations, but it doesn't verify ownership, and it shows an error page if the app isn't installed.
How does Expo Router handle deep links?
It matches the link's path to a file in app/. Use app/+native-intent.ts to rewrite paths that don't match a route.
Why does my link open the app on iOS but not Android?
Usually the fingerprint. The build on the phone was signed with a key whose SHA-256 isn't in assetlinks.json, often because Google Play re-signed it. Add the app signing key from Play Console.
Start with one link
The free plan has no time limit and needs no card. Create a project, add your app, and send yourself the link.