We ship an App Clip with our iOS app and want the App Clip card to appear when users share our website's links in Messages. Instead, recipients only get a plain link preview. The App Clip was approved and has been live on the App Store for over a week.
We've verified every requirement from the docs ("Associating your App Clip with your website" and the Messages invocation requirements):
- The invocation page's server-rendered HTML (no JS needed) contains the meta tag: apple-itunes-app with app-id and app-clip-bundle-id set correctly.
- /.well-known/apple-app-site-association has an "appclips" section listing the clip's app ID, and Apple's AASA CDN (app-site-association.cdn-apple.com/a/v1/<domain>) serves the same content.
- The App Clip's entitlements include appclips:<domain> and the correct parent application identifier.
- Via the App Store Connect API, the currently live build contains the APP_CLIP build bundle, and the live version has a default App Clip experience (action OPEN, with localizations).
- The default experience link https://appclip.apple.com/id?p=<clip-bundle-id> returns 200 and shows the clip.
- Tested in Messages between two devices whose owners are in each other's contacts, in brand-new conversations, on current iOS.
However, on-device App Clip diagnostics (Settings > Developer > App Clips Testing > Diagnostics) for the invocation URL show the "App Clip Published on App Store" and "Associated Domains" checks not passing, even though everything above is verified correct. ("No Advanced Experience registered" also appears, but as we understand it advanced experiences are only needed for QR/NFC/App Clip Codes, not Messages.)
Has anyone seen device-side association fail like this when the server-side config is demonstrably correct? Is there a known propagation delay after releasing a new app version, or a way to force the device to refresh its App Clip association cache beyond rebooting? Any pointers on what the diagnostics tool checks that isn't covered by the list above would be appreciated.