Mobile App Link Association Builder

How to use Mobile App Link Association Builder

Create selected Android assetlinks.json or modern iOS universal-link association source without contacting a website or device. Generate the actual domain-to-app association file you intend to host, while keeping Android package/fingerprint statements and iOS application/path components in one workflow. Syntax generation is separate from domain control, app signing and successful platform routing.

1. Provide optional association-model json, selected association model as json.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• One UTF-8 JSON model up to 50,000 bytes, 10,000 values and 40 levels. Unknown selected-model members, duplicate/prototype-related object members, malformed Unicode and prohibited controls are refused. Output is capped at 500,000 characters.
• A local module Worker loads the selected code and, for issue YAML, the writer library before ready within 10 seconds. Its separate computation deadline is 2 seconds. Nothing is rendered, fetched, submitted, published or automatically saved.
• Android model: {packageName,fingerprints}. The selected application-ID spelling uses at least two dot-separated components, each starting with an ASCII letter and continuing with letters/digits/underscore, at most 200 bytes overall. Supply 1–10 unique public signing-certificate SHA-256 fingerprints as 32 colon-separated hex bytes; hex is canonicalized to uppercase.
• Android output contains one android_app statement and fixed delegate_permission/common.handle_all_urls relation. The tool cannot infer the correct Play App Signing certificate, package ownership, manifest declarations, app build or device verification. Android dynamic rules and other relation types are outside this model.
• iOS model: {applicationIdentifiers,paths}. Use 1–10 unique exact entitlement identifiers: a selected 1–20-character alphanumeric prefix plus a dot and multi-component ASCII bundle ID, at most 220 bytes. Supply the actual application-identifier value; do not assume its prefix is always your Team ID.
• The paths array has 1–50 ordered {path,exclude?} components. Paths are nonblank slash-leading strings up to 500 UTF-8 bytes with no fragment marker/backslash; exclude is an actual boolean. The generator preserves this order and emits modern appIDs/components source. It does not evaluate wildcards, query/fragment components or actual URL matches.
• AASA uses an extensionless local download with binary transport MIME to prevent browsers from appending .json. Its bytes remain JSON; host it as application/json at the required extensionless HTTPS path. Host the reviewed artifact at its platform-defined .well-known path using the required HTTPS/content-type/no-redirect behavior. This tool does not make that deployment, fetch files, certify a domain/certificate/entitlement, refresh a platform CDN/device or guarantee universal-link handling. Web credentials, App Clips and legacy AASA paths are not generated.
• Structured text output is limited to 500,000 characters. Reduce the supplied source when that separate output budget is exceeded.
• Inputs are processed on this device and are not automatically saved or uploaded.