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.
In this repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-automationSkill
- consultingSkill
- contentSkill
- customer-successSkill
- data-analyticsSkill
- designSkill
- design-tokensSkill
- developmentSkill
- devopsSkill
- ecommerceSkill
- emailSkill
- expo-app-configSkill
- expo-config-pluginSkill
- expo-dev-clientSkill
- expo-eas-buildSkill
- expo-eas-submitSkill
- expo-modulesSkill
- expo-notificationsSkill
- expo-orchestratorSkill
- expo-prebuildSkill
- expo-routerSkill
- expo-troubleshootingSkill
- financeSkill
- frontend-tasteSkill
- marketingSkill
- market-researchSkill
- mobileSkill
- pentest-adSkill
- pentest-apiSkill
- pentest-bizlogicSkill
- pentest-bugbountySkill
- pentest-cicdSkill
- pentest-cloudSkill
- pentest-credentialsSkill
- pentest-ctfSkill
- pentest-detectionSkill
- pentest-engagementSkill
- pentest-exploit-chainSkill
- pentest-forensicsSkill
- pentest-llmSkill
- pentest-malwareSkill
- pentest-mobileSkill
- pentest-opsec-evidenceSkill
- pentest-orchestratorSkill
- pentest-privescSkill
- pentest-reconSkill
- pentest-reportSkill
- pentest-socialSkill
- pentest-stigSkill
- pentest-threat-modelSkill
- pentest-webSkill
- pentest-wirelessSkill
- productivitySkill
- productSkill
- salesSkill
- security-checkSkill
- securitySkill
- seo-crawl-budgetSkill
- seoSkill
- The first 60 shown.
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
- Distinctive: line 183
Use the fingerprint policy (auto runtime detection)
- Distinctive: line 185
Add a Sentry/Bugsnag release tag to the OTA payload — don't break error tracking
≈ “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.
Files
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:configureapp.json:
{
"expo": {
"runtimeVersion": { "policy": "appVersion" },
"updates": {
"url": "https://u.expo.dev/<project-id>",
"fallbackToCacheTimeout": 0,
"checkAutomatically": "ON_LOAD",
"enabled": true
}
}
}Channel ↔ Branch Model
| Build channel | Branch | Purpose |
| development | development | Dev client OTA |
| preview | preview | QA test |
| production | production | Production |
A single branch can be bound to different channels (eas channel:edit production --branch hotfix-1).
Runtime Version Policies
| Policy | How it's derived | Usage |
appVersion | expo.version | Native change = new build + new runtime |
sdkVersion | Expo SDK | SDK upgrade = new runtime (no longer recommended) |
nativeVersion | version+buildNumber | Every build a different runtime — OTA usually won't apply |
fingerprint | Native dependency fingerprint | Recommended: 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:listBranch 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-bugRollback Strategy
Method 1: Go back to the previous branch
eas channel:edit production --branch production-v1.2.0Method 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 100Embedded vs OTA Payload
| Scenario | Behavior |
eas update wasn't called in the build | The build ships with the embedded bundle |
eas update after the build | The device downloads and uses the OTA bundle |
| Device offline | The embedded bundle runs |
| New runtime version | OTA DOES NOT APPLY — a new build is required |
OTA limits: native code,
app.jsonplugin 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:listis empty fallbackToCacheTimeout: 0but 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
- Runtime version policy decision
- Branch/channel structure
- Update command (copy-paste)
- Rollout/rollback plan
- OTA-insufficient list (native-change check)
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
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.

