agentleFS
fatihkanfatihkan/badi/.claude/skills-vault/expo-eas-update/SKILL.md

expo-eas-update

Skill8 starsChanged 3 months agoMITView on GitHub

Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the fingerprint policy (auto runtime detection)

    line 183
  2. Distinctive:

    Add a Sentry/Bugsnag release tag to the OTA payload — don't break error tracking

    line 185

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

expo-eas-update

OTA (over-the-air) update publishing discipline with EAS Update. Channel/branch model, runtime-version strategy, rollback, and embedded vs OTA payload decisions. Build profiles live in expo-eas-build.

What It Does

  • Publishing JS/asset payloads with eas update
  • Channel ↔ branch mapping management
  • Runtime-version discipline (appVersion / sdkVersion / fingerprint / custom)
  • Branch management (preview, staging, production, feature/*)
  • Rollback and cohort/rollout-percent strategy
  • Embedded update vs OTA payload selection

Setup

npx expo install expo-updates
eas update:configure

app.json:

{
  "expo": {
    "runtimeVersion": { "policy": "appVersion" },
    "updates": {
      "url": "https://u.expo.dev/<project-id>",
      "fallbackToCacheTimeout": 0,
      "checkAutomatically": "ON_LOAD",
      "enabled": true
    }
  }
}

Channel ↔ Branch Model

Build channelBranchPurpose
developmentdevelopmentDev client OTA
previewpreviewQA test
productionproductionProduction

A single branch can be bound to different channels (eas channel:edit production --branch hotfix-1).

Runtime Version Policies

PolicyHow it's derivedUsage
appVersionexpo.versionNative change = new build + new runtime
sdkVersionExpo SDKSDK upgrade = new runtime (no longer recommended)
nativeVersionversion+buildNumberEvery build a different runtime — OTA usually won't apply
fingerprintNative dependency fingerprintRecommended: auto-detects whether native changed

fingerprint (the default recommendation in modern Expo):

"runtimeVersion": { "policy": "fingerprint" }

Publishing an Update

# Publish to a branch
eas update --branch production --message "fix: profile crash"

# Same name as the current Git branch
eas update --auto

# A single platform only
eas update --branch production --platform ios --message "iOS-only fix"

# Channel list
eas channel:list
eas branch:list

Branch Flow

# New branch
eas branch:create staging

# Bind to a channel
eas channel:edit production --branch production

# Switch channel (hotfix → switch to production)
eas channel:edit production --branch hotfix-2025-05

# Roll back
eas channel:edit production --branch production-pre-bug

Rollback Strategy

Method 1: Go back to the previous branch

eas channel:edit production --branch production-v1.2.0

Method 2: Republish the previous update

eas update:list --branch production
eas update:republish --branch production --group <previous-update-group>

Method 3: Rollout decrease

Publish the new update at 10%; if there's a problem, reset the rollout.

Rollout Control (cohort)

eas update --branch production --message "v1.2.1" --rollout-percentage 10
# 10% of devices receive it

# Increase
eas update:edit --branch production --rollout-percentage 50

# Full rollout
eas update:edit --branch production --rollout-percentage 100

Embedded vs OTA Payload

ScenarioBehavior
eas update wasn't called in the buildThe build ships with the embedded bundle
eas update after the buildThe device downloads and uses the OTA bundle
Device offlineThe embedded bundle runs
New runtime versionOTA DOES NOT APPLY — a new build is required

OTA limits: native code, app.json plugin changes, a new Expo SDK = OTA is NOT enough. Only JS/asset/JSON changes go over OTA.

Asset Selection

Exclude large assets from OTA:

{
  "expo": {
    "assetBundlePatterns": ["assets/icons/*"],
    "updates": {
      "assetPatternsToBeBundled": ["assets/critical/*"]
    }
  }
}

Lazy-fetch very large assets (video, models) with expo-asset — the OTA payload shrinks.

Client-Side Control

import * as Updates from "expo-updates";

useEffect(() => {
  async function check() {
    if (__DEV__) return;
    const u = await Updates.checkForUpdateAsync();
    if (u.isAvailable) {
      await Updates.fetchUpdateAsync();
      await Updates.reloadAsync();
    }
  }
  check();
}, []);

Best Practices

  • Use the fingerprint policy (auto runtime detection)
  • Rollout 10% → 50% → 100% for every production update
  • Add a Sentry/Bugsnag release tag to the OTA payload — don't break error tracking
  • Clarify the rollback plan before every release
  • Embedded bundle is critical (offline first launch)
  • Native change = new build, not OTA

Common Failure Patterns

  • Runtime version mismatch → OTA doesn't reach the device
  • Thinking a plugin change ships via OTA → it doesn't, a build is required
  • Channel not bound to a branch → update:list is empty
  • fallbackToCacheTimeout: 0 but first launch is offline → blank screen
  • State loss during reload → don't call reloadAsync() while the user is mid-action

Hard Refusal

  • Pushing harmful native-equivalent behavior without informing the user
  • Misuse: turning on an unauthorized data-collection feature flag via OTA
  • Shipping an update that violates compliance/store rules (ASC still expects the rules over OTA)

Output Format

  1. Runtime version policy decision
  2. Branch/channel structure
  3. Update command (copy-paste)
  4. Rollout/rollback plan
  5. OTA-insufficient list (native-change check)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.