Framework (OSS). 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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Framework (OSS). 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.
Requirements. Adding the App Clip target is open source. Shipping one requires an Apple Developer Program membership and App Store review, and the AASA file must be served over HTTPS on your domain (any HTTPS host works; EAS Hosting is one option). Building via EAS Build or bunx testflight uses your EAS plan's build minutes. See https://expo.dev/pricing and https://developer.apple.com/app-clips/.
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:
{
"expo"
:
{
"ios"
:
{
"bundleIdentifier"
:
"com.<username>.<app-name>"
,
"appleTeamId"
:
"XX57RJ5UTD"
}
}
}
2. Add the app clip target
bun create target clip
This installs @bacons/apple-targets, adds it to the plugins array in app.json, and writes:
targets/clip/expo-target.config.js, the target's config plugin
targets/clip/Info.plist, Clip Info.plist
targets/clip/AppDelegate.swift, Assets.xcassets, etc.
Pick a good icon or reuse the existing one defined in the app, check it with bunx expo config under the icon or ios.icon key.
3. Wire up associated domains
The parent app and the Clip each need the Associated Domains entitlement pointing at the domain that hosts the AASA file.
In app.json, add both applinks: (parent) and appclips: (Clip invocation) entries:
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().
./references/native-module.md, Local Expo module to detect App Clip context and present the SKOverlay install prompt
Submitting feedback
Only run this external write after explicit user authorization.
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.
