Skip to content

Commit 085c1c7

Browse files
authored
Merge pull request #304 from dubinc/mintlify/deep-links-troubleshooting-1773441031
Add troubleshooting section to deep links quickstart
2 parents 8ff84b7 + dd6e47f commit 085c1c7

1 file changed

Lines changed: 32 additions & 1 deletion

File tree

docs/concepts/deep-links/quickstart.mdx

Lines changed: 32 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -577,7 +577,7 @@ After they install and open your app, you'll need to use [deferred deep linking]
577577
Deep Linking](/docs/concepts/deep-links/deferred-deep-linking) guide.
578578
</Note>
579579
580-
## Test your deep links
580+
## Testing deep links
581581
582582
Before deploying your deep links to production, test them thoroughly using emulators to ensure they work correctly.
583583
@@ -615,3 +615,34 @@ You can also test your deep links by opening them from a messaging app on your d
615615
</Step>
616616
617617
</Steps>
618+
619+
## Troubleshooting deep links
620+
621+
If your deep links aren't working as expected, here are some common issues and solutions:
622+
623+
<Steps>
624+
<Step title="Deep link domain not allowlisted">
625+
626+
Make sure you've [allowlisted your deep link domain](/docs/concepts/deep-links/quickstart#allowlist-your-deep-link-domain-in-your-app) in your app's configuration. This is required for both iOS and Android to recognize and handle links from your domain.
627+
628+
</Step>
629+
630+
<Step title="iOS/Android cached outdated deep link configuration">
631+
632+
If you've completed all steps above and your deep links still aren't working, it's likely because iOS or Android cached the outdated deep link configuration.
633+
634+
Try uninstalling and reinstalling your app to clear the cache. This forces the operating system to re-fetch the `apple-app-site-association` or `assetlinks.json` files.
635+
636+
</Step>
637+
638+
<Step title="Deep link wrapped by a third-party links">
639+
640+
If your links are being shared through marketing platforms, email providers, or click trackers, the original URL may be getting wrapped or modified.
641+
642+
When a third-party service wraps your Dub link in their own tracking URL, the deep link won't work because the device sees the wrapper domain instead of your allowlisted domain.
643+
644+
Contact your marketing or analytics provider to ensure Dub links are passed through without modification.
645+
646+
</Step>
647+
648+
</Steps>

0 commit comments

Comments
 (0)