Testing and Troubleshooting

There are known limitations for testing flow during implementations. It's not possible to test the full flow of deferred links and universal app links unless your app is already in Play Store / App Store.

Testing iOS

If you are still in development mode and your app is not released to App Store, you can test SDK behavior by following steps:

1. Ensure the app is uninstalled on the device.
2. Visit the link on your device by pasting or typing its URL into your device's browser.
3. Platform will try to redirect to App Store page based on App Store ID you put in configuration. Your app might not exist at that moment.
4. Install you app in development mode like you normally do.
5. See the result. SDK should return the link you clicked if you managed to do it within the time window (currently 15 minutes).

Testing Android

In most cases referrer param is not passed to Play Store unless your production app is released. That means even though your app is displayed in Play Store for internal/external test, referrer probably won't work and so SDK won't use deterministic flow. However, still you can test probabilistic flow by following steps:

1. Ensure the app is uninstalled on the device.
2. Visit the link on your device by pasting or typing its URL into your device's browser.
3. Platform will try to redirect to Play Store based on package name. Your app might not exist at that moment.
4. Install you app in development mode like you normally do.
5. See the result. SDK should return the link you clicked if you managed to do it within the time window (currently 15 minutes).

You want to test referrer api in development mode, there are some workarounds for that.
Take a look on that medium article: link

Testing Android App Link

Once your app is installed, clicking a link in a messaging or notes app should automatically open it. If it doesn't, your Android certificate may be incorrect. Depending on your installation method, ensure you configure the correct SHA-256 fingerprint in the dashboard:

How you install the app	SHA-256 to use
Directly from EAS (Installing the .apk file)	EAS Fingerprint
Google Play Internal Testing (Installing via the Store)	Play Store App Signing Key
Local Development (Running npx expo run:android)	Debug Keystore (on your computer)

Common issues

• No match found (404):

  • Check timestamps — the click may be older than the match window.
  • Confirm the click was recorded (dashboard click logs).
  • For Android deterministic: confirm click_id is present in the referrer.

• 429 Too Many Requests:

  • Implement retry/backoff and ensure you are not using the same appID/key for heavy testing from many devices. Use staging keys.

• iOS clipboard prompt not appearing:

  • ensure shouldUseClipboard is enabled and that your app actually attempts to read the clipboard on first open.
  • ensure that on dashboard during iOS configuration you enabled copy link feature and then you copied link to clipboard after being redirected to special screen