WarpLink
SDKsAndroid

Deep Links

Handle Android App Links to route taps into the right screen, with cold start and warm start covered by the WarpLink SDK.

When a user taps a WarpLink URL and your app is installed, Android opens your Activity via App Links. The SDK resolves the URI into a WarpLinkDeepLink with the destination, custom parameters, and attribution data, then delivers it to the onLink callback you passed to configure().

configure() auto-registers ActivityLifecycleCallbacks, so cold start is automatic: a link that launches your app resolves and dispatches to onLink with no per-Activity code. Warm start (a link arriving while the app already runs) needs one line, because Android delivers it through onNewIntent. Both paths are gated by automaticDeepLinks, so opting out turns off the whole automatic model, not just cold start.

Set android:launchMode="singleTask" on the Activity so warm-start links reuse the running instance. Resolved links arrive in your onLink callback, always on the main thread.

Cold Start vs Warm Start

ScenarioEntry PointBehavior
Cold startApp not running: system launches ActivityHandled automatically. The link resolves and onLink fires
Warm startApp in background: brought to foregroundonNewIntent() forwards the intent via WarpLink.onNewIntent, then onLink fires

Your onLink callback receives a WarpLinkDeepLink:

Manual Resolution (Advanced)

To drive resolution yourself, set automaticDeepLinks = false in WarpLinkOptions and call handleDeepLink with the URI from intent?.data:

Error Handling

Verify assetlinks.json

WarpLink generates the Digital Asset Links file automatically. Verify it:

Check App Links verification status:

If App Links aren't verified, try uninstalling and reinstalling the app. Android re-verifies assetlinks.json at install time.

On this page