OTA updates
Ship compatible JavaScript and asset fixes without breaking installed binaries.
EAS Update can deliver JavaScript and bundled assets to an installed app. It cannot safely add a native module, permission, capability, config-plugin change, or other binary-incompatible behavior.
Prompt
Read agent-skills/add-ota-updates.md. Check whether this change is compatible
with the installed runtime. Publish it to preview first, test the matching
preview binary, then show me the exact update group, runtime, platforms, channel,
and source commit. Do not promote to production until I approve.Safe flow
- Complete EAS setup and keep
runtimeVersion.policy = appVersion. - Publish to the preview channel with a useful message.
- Test cold start, update fetch, restart, and offline launch on the matching binary.
- Promote the known update group instead of rebuilding from untested source.
- Use a staged rollout when risk warrants it.
- Watch crash/error and core funnel changes by update ID.
Keep a usable cached bundle offline. OTA must not bypass store rules, change the app's primary purpose, or silently introduce undisclosed data collection. When a native change is involved, increment the app version and ship a new store binary.