App Links are properly configured for Android

Without assetlinks.json published at /.well-known/assetlinks.json on your domain, Android cannot cryptographically verify that your app owns the domain, so the OS falls back to showing an app-chooser dialog (or opens the browser) every time a user taps an HTTPS link. This breaks email confirmation flows, referral links, and payment redirects — all of which depend on landing users directly in the app. The Android App Links spec (android-app-links) mandates both the JSON file and intent filter configuration; missing either half means app link verification fails silently in production.

Serve assetlinks.json at https://<your-domain>/.well-known/assetlinks.json with Content-Type: application/json. Get your SHA-256 fingerprint from your release keystore using keytool -list -v -keystore release.keystore.

[
  {
    "relation": ["delegate_permission/common.handle_all_urls"],
    "target": {
      "namespace": "android_app",
      "package_name": "com.yourcompany.appname",
      "sha256_cert_fingerprints": [
        "AA:BB:CC:..."
      ]
    }
  }
]

For Expo-managed builds, add the intent filter to app.json:

{
  "android": {
    "intentFilters": [
      {
        "action": "VIEW",
        "autoVerify": true,
        "data": [{ "scheme": "https", "host": "myapp.com" }],
        "category": ["BROWSABLE", "DEFAULT"]
      }
    ]
  }
}

autoVerify: true is required — without it, Android skips domain verification even if the file is present.