eas-update

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.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 interpreting version-specific behavior. If expo-updates is not installed, install the SDK-compatible version: Show more Installs 1.1K Repository expo/skills GitHub Stars 2.5K First Seen 6 days ago Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass