Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.
Instrucciones de origen · Vista previa de solo lectura
name
add-app-clip
description
Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.
Use this skill when you need add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.
Adds an iOS App Clip target to an Expo project. The Clip lives in targets/clip/, ships alongside the parent app, and is invoked from a URL on the app's domain via an Apple App Site Association (AASA) file.
The parent app's bundle ID becomes com.<username>.<app-name> and the Clip's is automatically derived as <parent>.clip (e.g. com.bacon.may20.clip).
1. Set bundleIdentifier and appleTeamId
bun create target warns if these are missing. Add to app.json:
Paste the JSON setup-safari printed, but add an appclips block for the Clip's full app ID (<TeamID>.<ClipBundleID>). The output of setup-safari only covers the parent app:
{"applinks":{"details":[{"appIDs":["XX57RJ5UTD.com.bacon.may20"],"components":[{"/":"*","comment":"Matches all routes"}]}]},"appclips":{"apps":["XX57RJ5UTD.com.bacon.may20.clip"]},"activitycontinuation":{"apps":["XX57RJ5UTD.com.bacon.may20"]},"webcredentials":{"apps":["XX57RJ5UTD.com.bacon.may20"]}}
Notes:
The file has no extension and no Content-Type requirements beyond being served as-is. Expo Router static export serves files in public/ verbatim.
The appclips block is what lets a URL on the domain launch the Clip.
webcredentials is used for sharing credentials between the website, parent app, and the App Clip.
Set up credentials for both targets (parent + Clip). Each gets its own provisioning profile but can share a single Distribution Certificate.
Sync capabilities — note Enabled: Associated Domains for the Clip target.
Build, upload, and schedule a TestFlight submission.
10. Configure App Clip metadata
Pull existing App Store metadata to local:
eas metadata:pull
Add apple.appClip to store.config.json. Up to 3 invocation URLs can launch the Clip from a web page:
{"configVersion":0,"apple":{"appClip":{"defaultExperience":{"action":"PLAY","releaseWithAppStoreVersion":true,"reviewDetail":{"invocationUrls":["https://may20.expo.app/",null,null]},"info":{"en-US":{"subtitle":"Instantly native with Expo","headerImage":"store/apple/app-clip/en-US/asc-app-clip.png"}}}}}}
The headerImage must be a 1800x1200 PNG with no opacity.
App Clip target: com.bacon.may20.clip, lives in targets/clip/
AASA hosted at https://may20.expo.app/.well-known/apple-app-site-association
Smart App Banner meta tag on every web route
Every route linked to its native counterpart
TestFlight build of the parent app with the Clip embedded
Once Apple invokes the Clip from a URL on the domain, iOS opens targets/clip/'s entry point which loads the React Native app.
Native detection (optional)
To let JS detect when it's running inside an App Clip and present an install prompt for the full app, create a local Expo module (bunx create-expo-module --local) that exposes navigator.appClip.prompt().
