---
title: "EAS Update: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/expo-eas-update/
description: "Publishes an Expo OTA update only after the channel, environment, runtime and native-build boundary are explicit."
---

# EAS Update: review, setup & limitations · Undominated.ai

> Publishes an Expo OTA update only after the channel, environment, runtime and native-build boundary are explicit.

[← Explore all skills](/skills/)

RELEASE ENGINEERING / Expo

# EAS Update

Publishes an Expo OTA update only after the channel, environment, runtime and native-build boundary are explicit.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/expo/skills/tree/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 5 linked sources
 Publisher Expo
 Licence [MIT ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/LICENSE)
 Revision d4f484024fec
 [Read what was—and wasn’t—checked ↓](#review)

“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.”

 [Expo · upstream description ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Publishing is treated as a remote mutation that needs an explicit project, channel, environment, platform, runtime, and message.
- Native changes are kept on the build path instead of being forced through an update.

### A good fit for

 - Publishing a JavaScript or asset update to a preview, staging, or production channel
- Debugging a release build that still shows old code after an update
- Diagnose why a native build does not receive an expected over-the-air update.

### Weigh up before choosing

 - The file says EAS Update has plan allowances and that publishing can affect installed apps.
- A missing eas.json must not be invented by hand; the CLI may send the user to eas build:configure.
- Runtime-version policy is not to be changed as an incidental fix for a mismatch.
- This review did not execute the skill.
- Changing a channel mapping affects all builds using that channel. A compatible JS update cannot add native APIs absent from the installed binary.
- The feedback command resolves a mutable latest npm package and can send supplied project/error context outside the local environment. Its package implementation and the separate feedback skill were not inspected or executed; this review does not establish what additional data they collect.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/expo/skills/eas-update/SKILL.md
- plugins/expo/LICENSE
- README.md

### Our findings

 - The pinned skill separates build, update, branch, and channel, and it says native-code or SDK changes still need a new build.
- Before edits it says to inspect package.json, the Expo config, eas.json, and whether ios/ or android/ are tracked, and to preserve existing channels.
- SDK 55 and later require an EAS environment when publishing, and the file says to check current CLI help before relying on remembered flags.
- Release builds may download an update in the background and apply it on a later cold start, so the debug section says to fully terminate and reopen rather than only background the app.
- The model distinguishes installed build, update, branch, channel and runtime version and directs configuration through the supported CLI with a reviewed diff.
- The final feedback section invokes submit-expo-feedback@latest with npm confirmation suppressed, sending supplied actionable context to Expo; repeated failures route to a separate expo-skill-feedback skill.

### Not established by this review

 - The skill was not executed inside a host agent.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/README.md)

DOCUMENTED COMMAND

 npx skills add expo/skills/plugins/expo/skills/eas-update Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/expo/skills/tree/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update Copy reviewed-revision command ↗ - The README documents npx skills@latest add expo/skills --skill '*'. That wildcard includes withheld skills.
- The command here pins only eas-update at the reviewed commit. The installer was not executed.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/expo-eas-update/bundle.zip and extract it into a new directory. It holds SKILL.md unchanged at revision d4f48402, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named eas-update. Keep SKILL.md and the licence together.
- The upstream directory also holds agents/openai.yaml (Codex display metadata and a default prompt); the bundle does not include it.

### Before you start

 - Node.js and npm
- An Expo project and EAS account before a real publish

### Compatibility

Claude Code · Codex · Cursor · GitHub Copilot · Cline

### Local instructions; publishing changes remote app updates

 - Read app config, eas.json, and native project presence
- Run eas update only after the channel, environment, platforms, runtime, and message are fixed
- Publish to EAS, which changes remote state
- Can publish bundles/assets and change update-channel mappings for installed users; authentication and release authority are required.
- Optional feedback can download/execute an npm package, contact Expo and transmit the context supplied in the report. It can also load a separate feedback skill; review that path before granting network or execution access.

### Cost model

MIT licence plus an Expo account; the skill says EAS Update publishing and delivery consume plan allowances.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download definition + licence ↗](/resources/skills/expo-eas-update/bundle.zip)[Raw Markdown ↗](/resources/skills/expo-eas-update/definition.md)
 ---
name: eas-update
description: "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."
version: 1.0.0
license: MIT
allowed-tools: "Bash(npx expo *), Bash(npx *eas-cli@*), Bash(eas *)"
---

# 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:

```bash
npx expo install expo-updates
```

Configure from the project root:

```bash
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.

If the command cannot proceed because the project is not linked or the user has not authorized the required remote operation, stop after any independently valid package installation and explain what remains. Do not partially reproduce `update:configure` by adding a runtime-version policy, config plugin, update URL, or channels by hand.

For dynamic app config, non-EAS builds, or a command that cannot complete automatically, follow the current setup documentation instead of guessing: https://docs.expo.dev/eas-update/getting-started.md.

## Keep the model straight

- **Build:** the installed native app. It contains native code, an embedded update, a platform, a runtime version, and normally a channel fixed at build time.
- **Update:** a published JavaScript bundle, assets, and metadata for one platform and runtime version.
- **Branch:** an ordered stream of updates. Its newest compatible update is active.
- **Channel:** a stable deployment target embedded in builds. On the server, it points to a branch.
- **Runtime version:** the compatibility boundary between an update and the native code in a build.

A build receives an update only when platform and runtime version match and the build's channel points to the branch containing that update:

```text
installed build (channel: production, runtime: 1.1.1, platform: ios)
 -> production channel
 -> production branch
 -> newest update for runtime 1.1.1 and ios
```

Channels and branches commonly have the same name, but they are separate objects. `eas channel:edit` changes a channel's server-side branch mapping for every build on that channel. It does not change an individual installation's embedded channel.

Use this model to make decisions, but explain only the concepts needed for the user's request rather than reciting the entire model every time.

## Decide whether an update is compatible

Use an update for changes to JavaScript, styling, and bundled assets that the installed native runtime already supports.

Create a new native build when a change adds or modifies native code or native configuration, including most native-library additions and SDK upgrades. Do not work around a runtime mismatch or imply that publishing can add native capabilities to an existing build. See https://docs.expo.dev/eas-update/runtime-versions.md.

Do not change the project's runtime-version policy as an incidental fix. Explain how the current policy affects compatibility; treat changing it as a separate decision because it changes which installed builds can receive future updates.

## Publish deliberately

Check the current CLI help before relying on remembered flags:

```bash
npx eas-cli@latest update --help
```

For the common channel-based flow:

```bash
npx eas-cli@latest update \
 --channel <channel> \
 --message "<message>" \
 --environment <environment>
```

SDK 55 and later require an EAS environment for publishing. Choose the environment intentionally so exported code receives the intended variables.

Publishing changes remote state and can affect installed applications. Before running it, establish the exact project, channel, environment, platforms, runtime version, and message. Publish to production only when the user has explicitly requested or approved it; if the authorization or target is ambiguous, stop before the command and ask. Do not infer a production destination solely from the current Git branch.

Prefer a preview or staging channel for validation. When promoting a tested update, use the documented deployment flow so production receives the same artifact where possible: https://docs.expo.dev/eas-update/deployment.md.

## Test according to the build type

### Development builds

Preview updates with the development build's Extensions UI, the EAS dashboard, or Expo Orbit. A normal `expo-dev-client` development build does not behave like a release build's automatic startup update flow.

### Preview, TestFlight, and production builds

Release builds normally prioritize startup speed. With the default launch behavior, the app may start its current embedded or cached update while downloading a newly published update in the background. The downloaded update is applied on a later restart.

For manual QA, fully terminate the app rather than backgrounding it, reopen it, allow the update time to download, and, if the change is not visible, fully terminate and reopen it once more. Describe this as **up to two cold launches**, not a TestFlight-specific ritual:

1. One launch can discover and download the update.
2. The following launch can run the downloaded update.

Do not automatically change `fallbackToCacheTimeout` to avoid the second launch. Waiting at startup trades launch latency and reliability for faster update activation. If the app needs an intentional update UX, consider the `expo-updates` APIs for checking, fetching, and presenting a non-blocking restart action. Use the `expo-updates` API reference for the project's detected SDK version.

## Debug a build that did not update

Check these in order:

1. Confirm the update was published to the intended EAS project, channel or branch, platform, and environment.
2. Compare the installed build's platform and runtime version with the published update.
3. Confirm the build actually contains the expected update URL and channel; app-config changes take effect only in a newly compiled build.
4. Inspect the channel-to-branch mapping and the active update on that branch.
5. Fully terminate the release build and allow for the normal download-then-apply lifecycle.
6. Use the current debugging guide for native logs, export problems, and configuration checks: https://docs.expo.dev/eas-update/debug.md.

Never bypass a compatibility or anti-bricking safeguard merely to make an update appear.

## Advanced and adjacent workflows

- **Channel surfing:** an individual release build can override its `expo-channel-name` request header to request another compatible channel. This differs from changing the server-side channel-to-branch mapping. Follow https://docs.expo.dev/eas-update/channel-surfing.md and preserve its access-control, persistence, recovery, and compatibility constraints.
- **Update health:** load `eas-update-insights` for adoption, launch failures, crash rate, payload size, and rollout monitoring after publishing.
- **Store releases:** load `eas-app-stores` when native changes require a new TestFlight, App Store, or Play Store build.

## Official references

- Setup: https://docs.expo.dev/eas-update/getting-started.md
- Concepts and matching: https://docs.expo.dev/eas-update/how-it-works.md
- Deployment: https://docs.expo.dev/eas-update/deployment.md
- Debugging: https://docs.expo.dev/eas-update/debug.md
- Current EAS CLI reference: https://docs.expo.dev/eas/cli.md

## Submitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
```bash
npx --yes submit-expo-feedback@latest --category skills --subject "eas-update" "<actionable feedback>"
```
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.

The download contains SKILL.md . Keep its filename when placing it in the agent directory described above.

By **Expo**. [Exact upstream source ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update/SKILL.md) · [Licence](/resources/skills/expo-eas-update/LICENSE.txt) · [Attribution](/resources/skills/expo-eas-update/ATTRIBUTION.txt)

SHA-256 d6ce6e300cf699c1995b5037c35daa56e8d2bf270191d2352fbcc006e9d41cfe

 Read the applicable licence The MIT License (MIT)

Copyright (c) 2025-present 650 Industries, Inc. (aka Expo)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Skill definition at reviewed revision ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update/SKILL.md) Checked 2026-10-14 https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update/SKILL.md Supports: summary, upstreamDescription, whySelected, limitations
- [Publisher README ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/README.md) Checked 2026-10-14 https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/README.md Supports: install, compatibility
- [Plugin MIT licence ↗](https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/LICENSE) Checked 2026-10-14 https://github.com/expo/skills/blob/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/LICENSE Supports: license
- [Skills installer tree URL parsing ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts) Checked 2026-10-07 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts Supports: install
- [2026-10-15 C2-W40 source re-review at the existing pin ↗](https://raw.githubusercontent.com/expo/skills/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/expo/skills/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/eas-update/SKILL.md Supports: upstreamDescription, review.notTested, review.reviewedAt

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Expo Design System ↗ Builds a token theme (color, spacing, typography, radius, shadow, motion) plus variant/size/state component conventions inside an Expo app, with grep-based drift audits and a named gallery of AI-generated-looking anti-patterns.](/skills/expo-expo-design-system/)[### Expo Module Authoring ↗ Scaffolds an Expo native module with an explicit slug, platform and feature set, then replaces the generated sample.](/skills/expo-expo-module/)[### Expo Web to Native Migration ↗ Migrates a web React codebase to a native Expo app screen by screen: native shell first, whole web UI shippable in DOM components on day one, then strangler-order nativization with device verification.](/skills/expo-expo-web-to-native/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
