Eas Update
Configure and use EAS Update for over-the-air JavaScript and asset updates with...
Install
npx skills add expo/skills --skill eas-update -g -a claude-code -y- Repository
- expo/skills4k
- Category
- Testing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,302 tokens
- Runs scripts
- No, instructions only
What it does
Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.
EAS Update
EAS service - costs apply. EAS Update is available on the Free plan; publishing and delivery use update, bandwidth, and storage allowances, with higher limits on paid plans. See https://expo.dev/pricing.
Use EAS Update to deliver compatible JavaScript, styling, and asset changes to installed apps without submitting a new native binary. Native-code changes still require a new build.
Start with the supported configuration path
Before changing anything, inspect package.json, the Expo app config, eas.json if present, and whether ios/ or android/ are tracked. Use what you find when reviewing the CLI's changes:
- Preserve existing dynamic or platform-specific app configuration.
- If
eas.jsonexists, preserve its profiles and existing channel assignments. The CLI adds a channel matching the profile name only to build profiles that do not already have one. - If
eas.jsonis absent, do not create it by hand. The CLI may direct the user to runeas build:configureseparately. - With tracked native projects, expect the CLI to synchronize the platform's native Update configuration. Without them, expect Continuous Native Generation to apply the native configuration during a later build.
Detect the Expo SDK version before installing packages or interpreting version-specific behavior.
If expo-updates is not installed, install the SDK-compatible version:
npx expo install expo-updates
Configure from the project root:
npx eas-cli@latest update:configure
Use eas update:configure rather than manually inventing updates.url, runtimeVersion, native metadata, or build-profile channels. The command understands EAS project linking, Continuous Native Generation, and projects with committed native directories. Review and explain its resulting diff.
