App Clip links and invocations

App Clips use the same association file as universal links, which means they inherit the same failure modes plus a few of their own.

6 August 2026 by PAD team

How invocation works

An App Clip is launched by a URL you register in the same apple-app-site-association file used for universal links, under a separate key:

{
  "appclips": {
    "apps": ["ABCDE12345.com.example.app.Clip"]
  }
}

The clip receives the invocation URL and decides what to show. Everything that breaks universal link verification breaks this too: redirects on the file, wrong content type, wrong identifiers.

Where clips are invoked

• App Clip Codes and QR codes, which work reliably because the camera opens them
• NFC tags, same
• Safari, through the Smart App Banner
• Messages and Maps, in specific contexts

Notice what is missing from that list: social apps. An App Clip URL tapped inside Instagram does not invoke the clip, because the in-app browser handles the navigation itself.

The practical consequence

If your App Clip strategy depends on links in social posts, it will not work the way the documentation implies. QR codes and physical placements are where clips genuinely shine, because the camera hands the URL to the system rather than to a WebView.

For social traffic, the realistic path is the ordinary one: get the tap out of the in-app browser and into the store or your app, which is a different mechanism entirely.

Testing

Use the local experience settings in developer options to test invocation without waiting for App Store Connect to propagate. Just remember that a local experience proves the clip runs, not that your association file is correct in production.