App Clips Q&A

We are encountering an issue with our App Clip invocation behavior: When attempting to invoke an Advanced App Clip Experience from a link in an email (digital invocation), the App Clip is not recognized. However, the Default App Clip Experience works correctly when invoked the same way. Interestingly, the Advanced App Clip Experience does launch successfully via physical invocation (scanning a QR code that encodes the same URL). Question: Is there any additional configuration required to enable an Advanced App Clip Experience for digital invocation (e.g., email, Messages, Safari), as opposed to physical invocation? Are there specific requirements—such as associated domains, Apple App Site Association (AASA) file setup, or App Store Connect configuration—that differ between digital and physical invocation methods?

My app is distributed through Unlisted App Distribution as it's for a specific audience. I was hoping to share a link to an App Clip experience to allow users to easily get started with it and the initial features, then allow them to install through StoreKit within the clip. When trying to open the App Clip, is shows the card, but I with an error: The operation could not be completed. (ASDErrorDomain error 507.)

I built an advanced app clip experience, associated it to a location, and its MATCHED. The status is marked (green) RECEIVED. However, I am unable to see the invocation on Maps. I don't see the buttons such as SUPPORT/ORDER shown for that place. The docs does not explain why. What is the exact requirement for us to surface buttons for POI? We are authorized by the businesses to add these for them. I'd love to hear in detail the exact process to add buttons for POI - how Uber Eats and Door Dash does it for restaurants and how their app clips get shown. Thank you.

Are there any plans to support multiple App Clips per app? Thank you.

Does the App Clip banner require the app to be live on the App Store, even for testing? Does Apple's CDN need time to cache/validate the AASA file, and is there a way to force re-validation? Are there known limitations with App Clip banners on non-production domains? Is there a diagnostic tool to verify our AASA file is being correctly read by iOS?

Xcode’s “App Thinning Size Report” reports a size under 15MB, but very close to it like 14.9MB, and if I publish the clip it becomes unavailable for costumers (They get "App Clip Unavailable" after scanning the QR code. On the other hand, if the size on the report is 14.7MB, it works fine for everyone. Can you advice a more accurate way to determine if the size is valid for distribution? On the same topic: Are there any plans to increase the size limit beyond the 15MB?

Will core motion ever be available to App Clips? Are there any workarounds for gathering device data. We use the camera and need to know coremotion data to verify the angles of the images coming in From the camera. We have an app that has some perfect use cases for app clips in measuring and returning results however we need the angles of the device for accuracy.

App Clips serve a useful purpose, a temporary or temporal mini app experience. I'd like to see this come to both unlisted and custom apps. Unlisted, easier argument. Same as public, just not searchable on the store. You need a link for an unlisted app ...... or an app clip code!!! For custom apps, a few use cases might be an internal conference that is short lived, or brief support sessions via a support app. The argument falls down for enterprise owned devices because why not just install everything you'd ever need--but for employee owned devices they can still enroll into an MDM, and we wouldn't want every single app available to be there. An app clip could be provisioned as eligible for that user / device and only there on-demand. FB11723876 - App Store Connect / App Clips: Add support to Unlisted and Custom Apps the ability to work with an App Clip (Oct 2022) Similar to https://developer.apple.com/forums/thread/832043 which was asking for just unlisted.

Renewing this request across another release cycle. App Clips remain unsupported on visionOS in 27 (Xcode 27 still can't create a visionOS App Clip target; the App Clips entry now showing in visionOS 27 Siri settings is a known issue per the beta release notes, FB178269460 — not the feature shipping). Background: FB13348462 (filed Nov 2023) Sep '24 thread (https://developer.apple.com/forums/thread/763818): an Apple engineer noted the request and invited more enhancement reports; a second developer added it would be a game-changer for teasing Vision Pro content. Why it matters: on iOS, App Clips are how we distribute native-quality AR/RealityKit experiences with the frictionlessness of a link — no full-app install. It's a core revenue driver. Our platform already runs the same experiences on Vision Pro, so App Clip support is the one missing piece. We've deferred multiple Vision Pro commercial projects (marketing activations, location-based and cultural-heritage installs) specifically because a visitor can't tap a code and drop into a spatial experience without installing a full app. Install-free entry is arguably more important on visionOS than iOS — walk-up headset experiences depend on it. Request: prioritize opening App Clips (or an equivalent link/code-triggered ephemeral launch) to third-party developers on visionOS. We've shipped this exact pattern on iOS at scale and would gladly act as a design partner / beta tester. Anyone else needing this: please file an enhancement report and paste the number here, per Apple's request in the original thread. Thank you!