Testing & Troubleshooting

Testing deferred linking has platform constraints. The complete deferred flow requires the store redirect chain, that is the App Store or Google Play.

Testing iOS

If your app is not yet released:

1. Remove any existing install from the device so the next open counts as a first launch.
2. Open a Detour link in a mobile browser.
3. Expect the App Store redirect to fail. With no public listing yet, the store has no listing to open, which does not affect the test.
4. Install your development build.
5. Launch the app and confirm the link resolves within the matching window (currently 15 minutes).

Testing Android

For non-production builds, the install referrer often does not work in store test tracks, so deterministic matching can be unavailable. You can still verify the probabilistic flow:

1. Uninstall the app from the device.
2. Open a Detour link in a mobile browser.
3. Expect the Play Store redirect to fail when the production listing is unavailable.
4. Install your development build.
5. Launch the app and confirm the link resolves within the matching window (currently 15 minutes).

For local install referrer testing workarounds, see How to test the Play Store Install Referrer API.

Missing click_id

If you encounter click_id missing in your build see limitations section Play Store referrer missing

Testing Android App Links

Whether an installed app opens a Detour link depends on the Dashboard SHA-256 matching the key that signed the build on your device:

Installation method	SHA-256 to configure	Where to find it
Google Play, any track	Play App Signing key	Play Console → Protected with Play → Manage Play app signing → App signing key certificate
eas build, any profile, including development	Keystore in your EAS account	eas credentials -p android → profile → Keystore → SHA256 Fingerprint
npx expo run:android / npx react-native run-android	Project’s android/app/debug.keystore	keytool -list -v -keystore android/app/debug.keystore -storepass android, or ./gradlew signingReport

To check any build directly: apksigner verify --print-certs app-debug.apk. The complete procedure is described in Finding your Android SHA-256 fingerprint.

Common issues

• No match found (404)
  • click is older than matching window
  • click was not recorded in Dashboard logs
  • for deterministic Android flow: missing click_id in referrer
• 429 Too Many Requests
  • add retry/backoff and avoid heavy testing with one key across many devices
• iOS clipboard prompt not appearing
  • check shouldUseClipboard: true
  • verify copy-link flow is enabled in Dashboard
• iOS Universal Link opens the browser instead of the app during development
  • before your domain and App Store listing have fully propagated, iOS resolves the apple-app-site-association file through Apple’s CDN, which may not have it yet
  • append ?mode=developer to the matching entry in your iOS associatedDomains (e.g. applinks:yourorg.godetour.link?mode=developer) so the device fetches the association file directly from your server, bypassing the CDN
  • this also requires enabling Developer Mode on the test device (Settings → Privacy & Security → Developer Mode). Remove the ?mode=developer suffix before shipping
• Link processed twice
  • confirm you call clearLink() after navigation
  • confirm exactly one DetourProvider instance is mounted

For integration patterns that are easy to test end-to-end, use Examples.