{"id":890,"date":"2026-04-23T17:00:00","date_gmt":"2026-04-23T22:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=890"},"modified":"2026-03-07T03:48:32","modified_gmt":"2026-03-07T08:48:32","slug":"expo-deep-linking","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/expo-deep-linking\/","title":{"rendered":"Expo Deep Linking: Setup Without Ejecting"},"content":{"rendered":"\n

Expo's managed workflow simplifies deep linking configuration by handling the native setup through app.json<\/code> (or app.config.js<\/code>). You don't need to touch Xcode or Android Studio directly. This guide covers deep linking setup in Expo, from basic scheme handling to Universal Links and App Links in production builds.<\/p>\n\n\n\n

For bare React Native setup, see React Native Deep Linking: Complete Setup Tutorial<\/a>. For navigation integration, see React Navigation Deep Links<\/a>.<\/p>\n\n\n\n

Understanding Expo's Linking Modes<\/h2>\n\n\n\n

Expo supports three types of deep links:<\/p>\n\n\n\n

1. Expo Go Links (Development Only)<\/h3>\n\n\n\n

During development with Expo Go, deep links use the Expo scheme:<\/p>\n\n\n\n

exp:\/\/192.168.1.5:8081\/--\/product\/123\n<\/code><\/pre>\n\n\n\n
These only work in development. You can't ship these to users.<\/p>\n\n\n\n
2. Custom URL Schemes<\/h3>\n\n\n\n
Links like yourapp:\/\/product\/123<\/code>. These work in development builds and production, but they're not as reliable as Universal Links\/App Links.<\/p>\n\n\n\n
3. Universal Links (iOS) \/ App Links (Android)<\/h3>\n\n\n\n
HTTPS links like https:\/\/go.yourapp.com\/product\/123<\/code>. These are the production standard and require domain configuration.<\/p>\n\n\n\n
Step 1: Configure app.json<\/h2>\n\n\n\n
Basic Scheme Configuration<\/h3>\n\n\n\n
Add a custom URL scheme to your app.json<\/code>:<\/p>\n\n\n\n
{\n  "expo": {\n    "scheme": "yourapp",\n    "ios": {\n      "bundleIdentifier": "com.yourapp",\n      "associatedDomains": ["applinks:go.yourapp.com"]\n    },\n    "android": {\n      "package": "com.yourapp",\n      "intentFilters": [\n        {\n          "action": "VIEW",\n          "autoVerify": true,\n          "data": [\n            {\n              "scheme": "https",\n              "host": "go.yourapp.com"\n            }\n          ],\n          "category": ["BROWSABLE", "DEFAULT"]\n        }\n      ]\n    }\n  }\n}\n<\/code><\/pre>\n\n\n\n
The scheme<\/code> field enables custom URL scheme handling (yourapp:\/\/<\/code>). The associatedDomains<\/code> and intentFilters<\/code> fields enable Universal Links and App Links for your custom domain.<\/p>\n\n\n\n
Using app.config.js for Dynamic Configuration<\/h3>\n\n\n\n
If you need environment-specific domains (staging vs production):<\/p>\n\n\n\n
\/\/ app.config.js\nconst IS_PROD = process.env.APP_ENV === 'production';\nconst LINK_DOMAIN = IS_PROD ? 'go.yourapp.com' : 'staging-go.yourapp.com';\n\nexport default {\n  expo: {\n    scheme: 'yourapp',\n    ios: {\n      bundleIdentifier: IS_PROD ? 'com.yourapp' : 'com.yourapp.staging',\n      associatedDomains: [`applinks:${LINK_DOMAIN}`],\n    },\n    android: {\n      package: IS_PROD ? 'com.yourapp' : 'com.yourapp.staging',\n      intentFilters: [\n        {\n          action: 'VIEW',\n          autoVerify: true,\n          data: [{ scheme: 'https', host: LINK_DOMAIN }],\n          category: ['BROWSABLE', 'DEFAULT'],\n        },\n      ],\n    },\n  },\n};\n<\/code><\/pre>\n\n\n\n
Step 2: Handle Incoming Links<\/h2>\n\n\n\n
Using expo-linking<\/h3>\n\n\n\n
Install the Expo linking module:<\/p>\n\n\n\n
npx expo install expo-linking\n<\/code><\/pre>\n\n\n\n
Handle deep links in your app:<\/p>\n\n\n\n
import * as Linking from 'expo-linking';\nimport { useEffect } from 'react';\n\nexport function useDeepLinks(onLink) {\n  useEffect(() => {\n    \/\/ Handle links that opened the app (cold start)\n    Linking.getInitialURL().then((url) => {\n      if (url) {\n        onLink(parseLink(url));\n      }\n    });\n\n    \/\/ Handle links while app is running (warm start)\n    const subscription = Linking.addEventListener('url', ({ url }) => {\n      onLink(parseLink(url));\n    });\n\n    return () => subscription.remove();\n  }, []);\n}\n\nfunction parseLink(url) {\n  const parsed = Linking.parse(url);\n  return {\n    path: parsed.path,\n    params: parsed.queryParams,\n  };\n}\n<\/code><\/pre>\n\n\n\n
Using expo-router (Recommended)<\/h3>\n\n\n\n
If you're using Expo Router (file-based routing), deep linking is mostly automatic. Expo Router maps URL paths to file paths:<\/p>\n\n\n\n
app\/\n  (tabs)\/\n    index.tsx       \u2192 \/\n    explore.tsx     \u2192 \/explore\n  product\/\n    [id].tsx        \u2192 \/product\/:id\n  invite\/\n    [code].tsx      \u2192 \/invite\/:code\n<\/code><\/pre>\n\n\n\n
The URL https:\/\/go.yourapp.com\/product\/123<\/code> automatically navigates to app\/product\/[id].tsx<\/code> with id = "123"<\/code>.<\/p>\n\n\n\n
To access the parameter in the screen:<\/p>\n\n\n\n
import { useLocalSearchParams } from 'expo-router';\n\nexport default function ProductScreen() {\n  const { id } = useLocalSearchParams<{ id: string }>();\n\n  return <Text>Product: {id}<\/Text>;\n}\n<\/code><\/pre>\n\n\n\n
With React Navigation (Non-Router)<\/h3>\n\n\n\n
If you're using React Navigation instead of Expo Router:<\/p>\n\n\n\n
import * as Linking from 'expo-linking';\n\nconst linking = {\n  prefixes: [\n    Linking.createURL('\/'),           \/\/ Custom scheme: yourapp:\/\/\n    'https:\/\/go.yourapp.com',        \/\/ Universal Links \/ App Links\n  ],\n  config: {\n    screens: {\n      Home: '',\n      Product: 'product\/:id',\n      Invite: 'invite\/:code',\n      Promo: 'promo\/:slug',\n      NotFound: '*',\n    },\n  },\n};\n\nfunction App() {\n  return (\n    <NavigationContainer linking={linking}>\n      <Stack.Navigator>\n        <Stack.Screen name="Home" component={HomeScreen} \/>\n        <Stack.Screen name="Product" component={ProductScreen} \/>\n        <Stack.Screen name="Invite" component={InviteScreen} \/>\n        <Stack.Screen name="Promo" component={PromoScreen} \/>\n        <Stack.Screen name="NotFound" component={NotFoundScreen} \/>\n      <\/Stack.Navigator>\n    <\/NavigationContainer>\n  );\n}\n<\/code><\/pre>\n\n\n\n
Step 3: Development Testing<\/h2>\n\n\n\n
Testing with Expo Go<\/h3>\n\n\n\n
In Expo Go, you can test custom scheme links using the Expo URL format:<\/p>\n\n\n\n
# Open a link in Expo Go (development)\nnpx uri-scheme open "exp:\/\/192.168.1.5:8081\/--\/product\/123" --ios\n<\/code><\/pre>\n\n\n\n
Or use Linking.createURL()<\/code> to generate the correct URL for the current environment:<\/p>\n\n\n\n
const url = Linking.createURL('product\/123');\nconsole.log(url);\n\/\/ In Expo Go: exp:\/\/192.168.1.5:8081\/--\/product\/123\n\/\/ In production build: yourapp:\/\/product\/123\n<\/code><\/pre>\n\n\n\n
Testing with Development Builds<\/h3>\n\n\n\n
For Universal Links testing, you need a development build (not Expo Go). Create one with:<\/p>\n\n\n\n
npx expo run:ios\n# or\nnpx expo run:android\n<\/code><\/pre>\n\n\n\n
Development builds include your native configuration (Associated Domains, intent filters), so Universal Links and App Links work as they would in production.<\/p>\n\n\n\n
Testing with EAS Build<\/h3>\n\n\n\n
For builds closer to production:<\/p>\n\n\n\n
eas build --platform ios --profile preview\neas build --platform android --profile preview\n<\/code><\/pre>\n\n\n\n
Install the preview build on a physical device and test links by tapping them from Messages, Notes, or email.<\/p>\n\n\n\n
Step 4: Domain Configuration<\/h2>\n\n\n\n
AASA File (iOS)<\/h3>\n\n\n\n
Your deep linking platform must serve the Apple App Site Association file at:<\/p>\n\n\n\n
https:\/\/go.yourapp.com\/.well-known\/apple-app-site-association\n<\/code><\/pre>\n\n\n\n
If using Tolinku, this is handled automatically. The file should include your Team ID and Bundle ID:<\/p>\n\n\n\n
{\n  "applinks": {\n    "apps": [],\n    "details": [\n      {\n        "appID": "TEAMID.com.yourapp",\n        "paths": ["*"]\n      }\n    ]\n  }\n}\n<\/code><\/pre>\n\n\n\n
assetlinks.json (Android)<\/h3>\n\n\n\n
Served at:<\/p>\n\n\n\n
https:\/\/go.yourapp.com\/.well-known\/assetlinks.json\n<\/code><\/pre>\n\n\n\n
Include your package name and signing certificate fingerprint. For EAS Build, you can find your fingerprint in the EAS dashboard or by running:<\/p>\n\n\n\n
eas credentials --platform android\n<\/code><\/pre>\n\n\n\n
Common Expo-Specific Issues<\/h2>\n\n\n\n
Expo Go Doesn't Support Universal Links<\/h3>\n\n\n\n
Expo Go uses its own URL scheme (exp:\/\/<\/code>). Universal Links and App Links only work in development builds or production builds. This is a common source of confusion: links work in testing (with the development build) but not in Expo Go.<\/p>\n\n\n\n
Config Plugin Changes Require Rebuild<\/h3>\n\n\n\n
When you change associatedDomains<\/code> or intentFilters<\/code> in app.json<\/code>, you need to rebuild the native project. These are native-level configurations that aren't applied by a JavaScript reload.<\/p>\n\n\n\n
# Rebuild after config changes\nnpx expo prebuild --clean\nnpx expo run:ios\n<\/code><\/pre>\n\n\n\n
Path Matching in Expo Router<\/h3>\n\n\n\n
Expo Router uses file-system routing. If your deep link path doesn't match a file in the app\/<\/code> directory, it will show the not-found route. Make sure your file structure matches your link paths.<\/p>\n\n\n\n
For example, if your links use \/product\/:id<\/code>, you need app\/product\/[id].tsx<\/code> (not app\/products\/[id].tsx<\/code>).<\/p>\n\n\n\n
Debugging Link Resolution<\/h3>\n\n\n\n
Add logging to verify links are being received:<\/p>\n\n\n\n
import * as Linking from 'expo-linking';\n\nLinking.addEventListener('url', ({ url }) => {\n  console.log('Received deep link:', url);\n});\n\nLinking.getInitialURL().then((url) => {\n  console.log('Initial URL:', url);\n});\n<\/code><\/pre>\n\n\n\n
Check the Metro bundler console or device logs for these messages when testing.<\/p>\n\n\n\n
Production Checklist<\/h2>\n\n\n\n