Deep Links and App Links: Verifying Ownership Without Breaking Review

Android App Links require a assetlinks.json file hosted on your domain to verify ownership before Android will treat your app as the default handler for that domain's links. A misconfigured or missing file doesn't block Play submission, but it does break the feature silently — users get a disambiguation dialog instead of automatic app opening.

The detail that's easy to miss: the assetlinks.json file needs to be served with the correct content type and be reachable without redirects, or Android's verification step will fail even if the file's content is correct.

The fix

Fix: test your App Links verification with Android's own Digital Asset Links API tool before assuming a correctly-formatted file is enough.

The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.

Keep going

assetlinks.json generator →

Generate the file, then validate the live deployment per-check.

Data Safety generator →

Turns these answers into a Play-ready CSV.

Short, specific submission fixes.

Run this check on your own AAB

Free analysis, exports when you need them.

Start free See pricing