Repository navigation
feat(ota): replace EAS Update with Codemagic Patch - #1
Conversation
Over-the-air updates now ship through Codemagic Patch, hosted for the OpenIAP team, instead of expo-updates and EAS Update. QA builds read the Staging deployment and store builds read Production; the public deployment keys live in shared/otaDeployments.json and reach the binary through the SDK's Expo config plugin. The cold-start gate keeps its bounded check and now confirms a healthy bundle with notifyAppReady so Patch does not roll an update back. A download that finishes after the splash budget waits for the next cold start instead of restarting mid-use, and the cold-start check records its attempt first so the soft update sheet cannot start a concurrent download. bun ota:release replaces eas:prod:updates with the same main, clean-tree, CI and compatibility gates, bundling with the production EAS environment through eas env:exec. Store binaries up to 1.4.0 still run expo-updates; the first Patch binary is 1.5.0.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Device gate: E2E resultNative wiring changed (expo-updates removed, Patch config plugin added), so device regression ran before review. QA builds (
Notes: the iOS log shows Not covered: signed store builds and the Production deployment (first Patch store binary is 1.5.0), and signed-in flows (no production credentials are entered by automation). |
Summary
Replace
expo-updates/ EAS Update with Codemagic Patch (@codemagic/react-native-patch0.7.0), hosted for the OpenIAP team athttps://ota.codemagicpatch.dev(appsBooKoo-iOS,BooKoo-Android).app.config.tsdropsruntimeVersion/updatesand adds the Patch config plugin. QA builds read theStagingdeployment, store builds readProduction. The deployment keys only let a build ask for updates, so they ship in every binary and live inshared/otaDeployments.json.coldStartUpdate.tsx), the soft update sheet, the recovery restart and the diagnostics screen now use Patch (checkForUpdate→downloadUpdate→installUpdate→restartApp,notifyAppReady,getRunningBundleUpdateMetadata).bun ota:release[:ios|:android](scripts/ota-release.zsh) replaceseas:prod:updates, keeping the main / clean-tree / CI / compatibility gates and bundling with the production EAS environment througheas env:exec.docs/ai/WORKFLOWS.mddescribe the Patch flow.Store binaries up to 1.4.0 still run expo-updates; the first Patch binary is 1.5.0, so OTA releases reach devices only after that store release.
Verification
bun check(227 suites, 1,740 tests) andbun lint:allpass locally.v1(see the gate comment below).