Publish OTA Update

Use this flow for compatible JavaScript, copy, style, and asset changes.

Preflight

Answer before publishing:

Change: <what changed>
Native code changed: <yes/no>
Native dependency changed: <yes/no>
Permission/app config changed: <yes/no>
Target runtime version: <value>
Target branch/channel: <preview/production>
Rollback plan: <command or previous update>
Store policy affected: <yes/no>

If any native answer is yes, build a new binary first.

Preview First

eas update --branch preview --message "Preview update"

Open a compatible preview build and verify the changed flow.

Production

eas update --branch production --message "Production hotfix"

Use rollout percentage when the risk justifies a staged rollout:

eas update --branch production --message "Gradual rollout" --rollout-percentage 10

Rollback

eas update:rollback

Rollback restores update selection. It does not undo a bad native binary already submitted to stores.

Warning: Never use OTA for payment behavior, privacy behavior, permission scope, or hidden native feature changes without checking store policy.