- Home
- Skills
- Mobile Development
- Expo OTA Updates: Ship or Build?
Works with the AI Agents you already use
Expo OTA Updates: Ship or Build?
EAS Update replaces the JS bundle and assets of an installed app without a store release.
Free
Expo OTA Updates: Ship or Build?
Example session with this skill installed
Can I ship everything since v1.0.0 to users tonight as an OTA update?
- Read your context and instructions
- Compiled the expo ota updates
No, not as an OTA update. The only commit since v1.0.0 is f09da8e feat: scan notes with the camera, and it needs a new store build.
Why it needs a build:
It adds expo-camera, which contains native code. The v1.0.0 build that users have installed doesn't include it, so the JS that calls the camera would crash or fail on their devices. The change checker returned exit code 1, meaning a build is required.
The other three changed files are plain JS/TS (App.tsx, src/scan.tsx), but they only exist to use the camera. There's no separate fix in there that could go out on its own.
It's a new feature, not a fix. Even with no native code involved, adding camera scanning over the air is the kind of change Apple's guidelines 2.3.1(a) and 2.5.19 say must go through App Review.
Your setup also isn't ready for OTA updates, so please don't publish anything tonight:
1.
app.json has no runtimeVersion. Updates aren't matched to the native code in a build, so a bundle that needs expo-camera could reach v1.0.0 users and crash the app. Add "runtimeVersion": { "policy": "fingerprint" }.
2.
The production profile in eas.json has no channel. The v1.0.0 build probably isn't listening for updates at all. Add "channel": "production".
3.
The production profile has "developmentClient": true. That turns your store build into a development client, which Apple would likely reject. Check how v1.0.0 was actually built before you rebuild.
Things to fix before the 1.1.0 build:
ios.infoPlist.NSCameraUsageDescriptionis an empty string. Apple rejects apps without a real explanation of why the camera is needed, e.g. "Scan your paper notes into the app."- Consider adding
expo-cameratopluginswith its permission options, so the iOS and Android permissions are set up through config. - Bump
versionto 1.1.0.
The path forward: make the config fixes above, cut a 1.1.0 production build, and submit it for review. Once that build is live and has a runtime version and channel, you can ship future JS-only fixes as OTA updates. Each one should start small, e.g. eas update --channel production --environment production --rollout-percentage 10, with eas update:rollback ready if something goes wrong.
I can make the app.json and eas.json changes and run a release check before the build if you want.
Connects securely to your tools. The creator never sees your data.
About this skill
EAS Update replaces the JS bundle and assets of an installed app without a store release. That's powerful and easy to misuse: an update that calls native code missing from the installed binary crashes, an update published to the wrong channel reaches nobody, and a feature switched on over the air without review is exactly what Apple's guideline 2.5.19 now punishes.
What it does
- OTA-or-build check (
scripts/ota-or-build.mjs, zero-dependency Node 18+ and git): diffs two refs (default: latest tag → working tree) and gives a verdict with reasons.- New or upgraded packages with native code, checked in node_modules (ios/, android/, expo-module.config.json, app.plugin.js)
- Native app.json keys, config plugins, patch-package patches that touch native files, icons
- Exit codes: 0 = OTA is fine, 1 = needs a build, 3 = unsure, verify with
eas fingerprint:compare
- Setup guide: runtimeVersion policies (fingerprint / appVersion), channels and branches, publishing with the right
--environment. - Rollouts and rollbacks: percentage rollouts,
eas update:rollback, and what to check when users don't receive an update or the app crashes after one.
Output
A yes/no answer with the reasons, what to fix in your update setup, and the exact eas update command (with a small rollout) when an update is safe.
Checked against the EAS Update docs and Expo SDK 58 on 29 Oct 2026.
Open source (MIT): https://github.com/disconnectuss/expo-ship-kit.skills. Part of expo-ship-kit.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
The OTA-or-build check is a heuristic over the git diff: it's explainable, not a full native fingerprint. When it's unsure (exit code 3) or the stakes are high, confirm with eas fingerprint:compare. It can't see which builds your users actually have installed. Needs Node.js 18+ and git.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed today
- Free with an Agensi account
- Software
Node.jsexpo
Git
- Optional
- EAS CLI (only for the commands it suggests)
Permissions
Terminal: runs `node scripts/ota-or-build.mjs`, which calls read-only git commands on your repo (`git diff --name-only`, `git describe`, `git show`, `git rev-parse`, `git ls-files`). Read Files: package.json, app config and node_modules package folders, to see whether a dependency ships native code. No network calls. Nothing is sent anywhere.