Testing
Deep links behave differently depending on the platform, so run through each scenario below before shipping.
Quick Checklist
✅ Deep Link Services enabled in Essential Kit Settings
✅
OnCustomSchemeUrlOpenand/orOnUniversalLinkOpenhandlers registered before gameplay starts✅ Device has a build that matches the deep link configuration
✅ Link you are testing uses the same scheme/host/path defined in settings
Mobile Device Testing
iOS (Devices and Simulator)
Build and install your app on the target device or simulator.
Open Safari and visit a simple HTML page that contains your link:
<a href="mygame://invite/friend123">Join my match</a>Tap the link. If the app is installed, iOS should foreground your game and fire the relevant deep link event.
On simulator you can also trigger links from the command line:
xcrun simctl openurl booted "mygame://invite/friend123"For universal links, make sure your
apple-app-site-associationfile is reachable over HTTPS before testing.
Android (Devices and Emulator)
Build and install your app on the device or emulator.
Use Chrome or any browser to open a test page with your link or type the URL directly into the address bar.
Android should display a chooser the first time; pick your app and select Always to skip future prompts.
You can also launch from
adb:adb shell am start -W -a android.intent.action.VIEW -d "mygame://invite/friend123"For Android App Links (https), verify that your
assetlinks.jsonfile is accessible. Useadb shell amwith the https URL to confirm the association.
Debugging Tips
If no event fires, confirm
DeepLinkServices.IsAvailable()returnstrueand the feature is enabled in build settings.Mismatched schemes, hosts, or paths are the most common cause of silent failures—double-check spelling and casing.
Universal links cache the first valid association per install. Uninstall the app before testing changes to the hosted files.
Last updated
Was this helpful?