eas-update
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.
Target: Mobile development. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- EAS Update
- Start with the supported configuration path
- Keep the model straight
- Decide whether an update is compatible
- Publish deliberately
- Test according to the build type
- Development builds
- Preview, TestFlight, and production builds
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. 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.json exists, 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.json is absent, do not create it by hand. The CLI may direct the user to run eas build:configure separately. 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 int
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- expo/skills
- Source file
- plugins/expo/skills/eas-update/SKILL.md
- Fixed revision
- a9e5bd3fa00b4e61f632e43f85da73aee1942582
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: Expo Skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:42.032Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.