feat(updates): wire EAS Update for OTA content drops - #27
Merged
Merged
Conversation
Adds expo-updates (SDK 53 line) with a pinned runtime version and a production channel baked into builds, so monthly drill/mascot/theme drops publish over the air without a Play release. Native config is synced via prebuild; CI regenerates it from app.json as before.
The versionless kotlin-gradle-plugin on the classpath resolves to 2.0.21 via RN 0.79's gradle plugin, but the stale 1.9.25 ext made expo-updates select KSP 1.9.25-1.0.20, which crashes against KGP 2.0.x internals (NoSuchMethodError: KspTaskJvm.getChangedFiles). 2.0.21 matches the SDK 53 template and selects KSP 2.0.21-1.0.28.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds over-the-air JS updates so monthly content drops (drills, mascots, court themes — all JS) ship without a Play release.
What's wired
expo-updates@0.28.18(SDK 53 line); lockfile diff reviewed — no react drift, no expo packages nested off the root@haritabh1992/badminton-court-simulatorwithupdates.url+ project ID in app.json; channelproduction→ branchproductioncreated on EASupdates.requestHeaders(required for gradle-built binaries)Runtime version discipline
expo.runtimeVersionis a manually pinned string ("1.0.0") —eas updaterejects version policies with a checked-inandroid/dir. Bump it in any release that changes native code; leave it for JS-only releases so one publish reaches every compatible store build.Activation
No live build can receive updates yet (2.8.0/vc18 shipped with updates disabled). The next tag release (2.8.1/vc19, already bumped on main) ships the update client. After that, a content drop is just:
Publish pipeline already verified end to end against a throwaway EAS branch (accepted for runtime 1.0.0, branch deleted after).