iOS / Android Dev Tools
Paste a file, test several HTTPS URLs or paths, and inspect each app ID's deciding rule. No domain is fetched.
Edit the example, then validate.
Validation runs in this browser tab. The tool does not request the pasted domains or URLs.
Leave empty to report every declared App ID; an exact ID limits the results.
Edit the example, then validate.
An AASA validator is useful before publishing an association file or when one product link opens the app while another stays in Safari. A JSON syntax check alone cannot explain which ordered rule claimed a URL.
This Apple App Site Association validator reports the rule and App ID chosen from the text you pasted. It separates local matching from server hosting, Apple CDN state and the behavior of an installed iPhone app.
The AASA validator sends several URL paths through the same ordered rule list and separates included, excluded and unmatched outcomes. This reveals a path mistake before the file is deployed.
A broad rule placed first can claim a URL before a later exclusion is reached. The AASA validator shows the deciding rule index and warns when a catch-all shadows later entries.
Paste the full JSON, including applinks.details. The example uses modern appIDs and components; legacy appID and paths also work. A syntax error points to its line and column.
Enter one HTTPS URL or slash-led path per line. Leave the App ID filter empty to see every declared app; changing any input makes the previous report stale until you validate again.
Inspect each result's details and rule index before exporting. A green local match means that the pasted rules selected an app, while every hosting and device item remains marked Not checked.
Compare components with path, query, fragment and exclude conditions, or test older paths with ordered NOT exclusions. This Universal Link tester keeps the two formats distinct.
Run the same URL against every declared ID or select one exactly. An absent ID is reported separately from a valid ID whose paths do not match.
The AASA path checker records findings, input line numbers, deciding rule indices and a deployment checklist in a JSON report for release review.
A local AASA validator can show that the pasted path includes a URL, but iOS also depends on the hosted file, CDN copy, Associated Domains entitlement, app installation and how the link was opened. Use the deployment list and then test on a device.
Paste the association JSON and one or more HTTPS URLs here. The rule trace identifies the first matching component or paths entry, including exclusions. It predicts the JSON decision, not an installed app launch.
Yes. Older details entries use appID with paths, while newer entries can use appIDs with components. This page evaluates either style in a details entry and reports mixed or unsupported forms as undecidable.
Order matters. A broad include rule before a narrower exclude can win first, so the later exclusion is never reached. Put the exclusion before the catch-all and test the exact URL again.
No. The AASA validator does not make network requests. Check the CDN copy and real device separately after deployment; the local checklist does not claim those checks passed.
Still stuck on a rule?
Test a real URL against the intended app ID, then carry the unchecked deployment items into your release review.