PER-UPDATE ROLLOUT · PRODUCTION

Ship a JS update to 10%, watch it, then decide

This assumes the change is JavaScript or bundled assets and matches the production builds’ channel, platform, and runtime version.

1 · PROVE ITVerify on preview

Test the exact user journey on compatible iOS and Android preview builds.

eas update \ --channel preview \ --environment preview \ --message "Verify checkout fix"

→

2 · LIMIT EXPOSUREStart at 10%

Ten percent receive the new update; the other 90% stay on the previous compatible update.

eas update \ --channel production \ --environment production \ --rollout-percentage=10 \ --message "Checkout fix"

→

3 · OBSERVECompare the new update with the prior release

Filter dashboards to production, this OTA update, each platform, and a useful time window. Wait for enough real launches and affected user journeys to judge it.

eas update:list
eas update:view [UPDATE_GROUP_ID]

What I would watch before increasing exposure

💥Errors and crashesNew JavaScript errors, native crashes, error rate, and affected sessions.

🚀Startup healthCold/warm launch, bundle load, first render, and time to interactive—especially P90/P99.

⬇️Update deliveryDownload time, successful uptake, and whether both iOS and Android are receiving it.

🎯Critical journeyLogin, checkout, save, sync, or the exact feature changed. Watch failures and completion rate.

📣User signalsSupport messages, reviews, analytics anomalies, and device/OS-specific complaints.

Healthy → increase to 100%No meaningful regression, the changed journey works, and coverage includes both platforms and representative devices.

eas update:edit
# select the rollout and set 100%

Health gate

Regression → revertStop exposure when errors, crashes, startup, or the changed journey materially worsen.

eas update:revert-update-rollout

Operational constraint: only one update with a given runtime version can be rolling out on a branch at a time. Finish it at 100% or revert it before publishing another update for that runtime.

Expo Rollouts · EAS Observe dashboard · Rollbacks