Update to Expo

{
  "name": "expo-app-clip",
  "description": "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 426
    },
    {
      "relative_path": "references/native-module.md",
      "size_in_bytes": 2305
    }
  ],
  "skill_md_contents": "---\nname: expo-app-clip\ndescription: 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.\n---\n\n# Add an App Clip to an Expo App\n\n> **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/.\n\nAdds 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.\n\nThe 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`).\n\n## 1. Set `bundleIdentifier` and `appleTeamId`\n\n`bun create target` warns if these are missing. Add to `app.json`:\n\n```json\n{\n  \"expo\": {\n    \"ios\": {\n      \"bundleIdentifier\": \"com.<username>.<app-name>\",\n      \"appleTeamId\": \"XX57RJ5UTD\"\n    }\n  }\n}\n```\n\n## 2. Add the App Clip target\n\n```sh\nbun create target clip\n```\n\nThis installs [`@bacons/apple-targets`](https://github.com/EvanBacon/expo-apple-targets), adds it to the `plugins` array in `app.json`, and writes:\n\n- `targets/clip/expo-target.config.js` — the target's config plugin\n- `targets/clip/Info.plist` — Clip Info.plist\n- `targets/clip/AppDelegate.swift`, `Assets.xcassets`, etc.\n\nPick 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.\n\n## 3. Wire up associated domains\n\nThe parent app and the Clip each need the Associated Domains entitlement pointing at the domain that hosts the AASA file.\n\nIn `app.json`, add both `applinks:` (parent) and `appclips:` (Clip invocation) entries:\n\n```json\n{\n  \"expo\": {\n    \"ios\": {\n      \"associatedDomains\": [\n        \"applinks:may20.expo.app\",\n        \"appclips:may20.expo.app\"\n      ]\n    }\n  }\n}\n```\n\nIn `targets/clip/expo-target.config.js`, declare the Clip's entitlement:\n\n```js\n/** @type {import('@bacons/apple-targets/app.plugin').ConfigFunction} */\nmodule.exports = (config) => ({\n  type: \"clip\",\n  icon: \"https://github.com/expo.png\",\n  entitlements: {\n    \"com.apple.developer.associated-domains\": [\"appclips:may20.expo.app\"],\n  },\n});\n```\n\n> If you skip this, `expo prebuild` will print: `Apple App Clip may require the associated domains entitlement but none were found`.\n\n## 4. Register bundle IDs and create the App Store entry\n\n```sh\nbunx setup-safari\n```\n\nThis logs in to the Apple Developer account, registers `com.bacon.may20`, creates the App Store Connect entry, and prints:\n\n- A starter `apple-app-site-association` JSON\n- A `<meta name=\"apple-itunes-app\">` tag with the iTunes app id\n- Team ID, iTunes ID, and Bundle ID\n\n## 5. Host the AASA file\n\nApp Clips are invoked when iOS fetches `https://<your-domain>/.well-known/apple-app-site-association` and finds a matching `appclips` entry.\n\n```sh\nmkdir -p public/.well-known\ntouch public/.well-known/apple-app-site-association\n```\n\nPaste 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:\n\n```json\n{\n  \"applinks\": {\n    \"details\": [\n      {\n        \"appIDs\": [\"XX57RJ5UTD.com.bacon.may20\"],\n        \"components\": [{ \"/\": \"*\", \"comment\": \"Matches all routes\" }]\n      }\n    ]\n  },\n  \"appclips\": {\n    \"apps\": [\"XX57RJ5UTD.com.bacon.may20.clip\"]\n  },\n  \"activitycontinuation\": {\n    \"apps\": [\"XX57RJ5UTD.com.bacon.may20\"]\n  },\n  \"webcredentials\": {\n    \"apps\": [\"XX57RJ5UTD.com.bacon.may20\"]\n  }\n}\n```\n\nNotes:\n\n- The file has **no extension** and **no `Content-Type` requirements** beyond being served as-is. Expo Router static export serves files in `public/` verbatim.\n- The `appclips` block is what lets a URL on the domain launch the Clip.\n- `webcredentials` is used for sharing credentials between the website, parent app, and the App Clip.\n- `activitycontinuation` is optional and used for sharing the link between mobile and desktop. Must be used with `Head` from expo-router — see https://docs.expo.dev/router/advanced/apple-handoff/\n- Notation and route-disabling details: https://sosumi.ai/documentation/xcode/supporting-associated-domains\n\n## 6. Add the Smart App Banner meta tag\n\nCreate `src/app/+html.tsx` (Expo Router's HTML shell) and add the tag from `setup-safari`. Create the versioned template if it doesn't exist:\n\n```sh\nbunx expo customize src/app/+html.tsx\n```\n\nAdd the meta tag to the `<head>`:\n\n```tsx\nimport { ScrollViewStyleReset } from \"expo-router/html\";\n\nexport default function Root({ children }: { children: React.ReactNode }) {\n  return (\n    <html lang=\"en\">\n      <head>\n        <meta charSet=\"utf-8\" />\n        <meta httpEquiv=\"X-UA-Compatible\" content=\"IE=edge\" />\n        <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\" />\n        <meta name=\"apple-itunes-app\" content=\"app-id=6771566491\" />\n        <ScrollViewStyleReset />\n      </head>\n      <body>{children}</body>\n    </html>\n  );\n}\n```\n\nTo make the website show the App Clip card instead of the install card, use:\n\n```html\n<meta\n  name=\"apple-itunes-app\"\n  content=\"app-id=6771566491, app-clip-bundle-id=com.bacon.may20.clip, app-clip-display=card\"\n/>\n```\n\n## 7. Deploy the website\n\nThe AASA file must be live before iOS will trust the association. Use [EAS Hosting](https://docs.expo.dev/eas/hosting/):\n\n```sh\nbunx expo export -p web\neas deploy --prod\n```\n\nThis publishes the site (including `/.well-known/apple-app-site-association`) at `https://<slug>.expo.app`. Verify:\n\n```sh\ncurl https://may20.expo.app/.well-known/apple-app-site-association\n```\n\n## 8. Mirror permissions\n\nInspect the parent app's permissions after prebuild:\n\n```sh\nnpx expo config --type introspect\n```\n\nLook at the `infoPlist` object — mirror the permission keys in the App Clip's `Info.plist` so matching APIs can be used from the Clip.\n\nSet `deploymentTarget: \"17.6\"` in the Clip's target config — App Clips have a higher minimum size limit in iOS 17.6.\n\nIf the app uses push notifications or location services, add to the App Clip's `Info.plist` to request the necessary permissions:\n\n```xml\n<key>NSAppClip</key>\n<dict>\n  <key>NSAppClipRequestEphemeralUserNotification</key>\n  <false/>\n  <key>NSAppClipRequestLocationConfirmation</key>\n  <true/>\n</dict>\n```\n\n## 9. Build and submit to TestFlight\n\n```sh\nbunx testflight\n```\n\nThis will:\n\n1. Generate an `eas.json` if missing.\n2. Set up credentials for **both** targets (parent + Clip). Each gets its own provisioning profile but can share a single Distribution Certificate.\n3. Sync capabilities — note `Enabled: Associated Domains` for the Clip target.\n4. Build, upload, and schedule a TestFlight submission.\n\n## 10. Configure App Clip metadata\n\nPull existing App Store metadata to local:\n\n```sh\neas metadata:pull\n```\n\nAdd `apple.appClip` to `store.config.json`. Up to 3 invocation URLs can launch the Clip from a web page:\n\n```json\n{\n  \"configVersion\": 0,\n  \"apple\": {\n    \"appClip\": {\n      \"defaultExperience\": {\n        \"action\": \"PLAY\",\n        \"releaseWithAppStoreVersion\": true,\n        \"reviewDetail\": {\n          \"invocationUrls\": [\"https://may20.expo.app/\", null, null]\n        },\n        \"info\": {\n          \"en-US\": {\n            \"subtitle\": \"Instantly native with Expo\",\n            \"headerImage\": \"store/apple/app-clip/en-US/asc-app-clip.png\"\n          }\n        }\n      }\n    }\n  }\n}\n```\n\nThe `headerImage` must be a 1800x1200 PNG with no opacity.\n\nPush back to the store:\n\n```sh\neas metadata:push\n```\n\nApple's recommended App Clip metadata guidelines: https://sosumi.ai/documentation/appclip/configuring-the-launch-experience-of-your-app-clip\n\n## What you get\n\n- Parent app target: `com.bacon.may20`\n- App Clip target: `com.bacon.may20.clip`, lives in `targets/clip/`\n- AASA hosted at `https://may20.expo.app/.well-known/apple-app-site-association`\n- Smart App Banner meta tag on every web route\n- Every route linked to its native counterpart\n- TestFlight build of the parent app with the Clip embedded\n\nOnce Apple invokes the Clip from a URL on the domain, iOS opens `targets/clip/`'s entry point which loads the React Native app.\n\n## Native detection (optional)\n\nTo 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()`.\n\nSee [./references/native-module.md](./references/native-module.md) for the Swift module, TypeScript interface, and usage.\n\n## References\n\n- ./references/native-module.md — Local Expo module to detect App Clip context and present the SKOverlay install prompt\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-app-clip\" \"<actionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf 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.\n"
}