App linking
Mobile and PWA discovery files that mishandle the strict format requirements iOS, Android, and browsers enforce.
iOS universal-links manifest (AASA). Apple is famously strict about the Content-Type, JSON validity, appID format (TEAMID.bundle.id), and the paths array. These modes break each of those expectations.
Android App Links manifest. Android verifies app links by checking SHA-256 fingerprints, package_name, and relation strings against a strict schema. These modes break each of those.
PWA web app manifest. Wide tooling consumption — Chrome, Lighthouse, browser PWA installers all parse this and complain when it's wrong. Modes break required icons, start_url, display modes, colors, or name fields.
iOS, Android, and PWA installers all auto-discover or read these files from canonical paths. Each platform has its own strict format. Real-world bugs in app linking are common and frustrating to diagnose because the failure mode is usually silent: the OS simply doesn’t recognise the app as the handler for the URL, or the install prompt never appears.
Point your build pipeline’s link-verification step or your PWA tooling at these endpoints to confirm it surfaces the failure clearly rather than failing closed.