chore(example): upgrade Expo SDK 55 to 57#10
Merged
Conversation
SDK 57 maps to react-native 0.86 / react 19.2.3; expo-location, expo-secure-store, expo-sensors and babel-preset-expo realigned via `expo install --fix`. Root devDeps follow so `bob build` and tsc typecheck against the same RN the example runs. - `newArchEnabled` removed from app.json: SDK 57 dropped the key from the schema — the new architecture is the only architecture. - example standardized on yarn (README already instructs `yarn install`); the stale package-lock.json predated that and made expo's package-manager detection ambiguous. Peer range (react-native >=0.79.0) needs no widening — 0.86 is inside. Verified: expo-doctor 20/20, `expo prebuild --clean` with all plugin injections intact, `expo run:ios` + `expo run:android` build, launch and render with the native module responding on both platforms. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012rn1KYa8uH8ikwK3AaHaLP
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.
Stacked on #9 (merges into that branch; GitHub retargets to main when #9 lands).
Upgrades the example dev-client app two Expo majors (55 → 57 = react-native 0.86, react 19.2.3) and aligns the root devDeps with it.
expo install expo@^57.0.0+expo install --fixrealignedexpo-location,expo-secure-store,expo-sensors,babel-preset-expo.newArchEnabledremoved from app.json — SDK 57 dropped the key (new arch is the only arch).package-lock.jsonpredated the README'syarn installinstructions and made Expo's package-manager detection ambiguous;yarn.lockis now committed instead.react19.2.3,react-native0.86.0,@expo/config-plugins~57.0.3) sobob build/tsc check against the RN the example runs. Peer range (>=0.79.0) unchanged.Heads-up from SDK 56 (intermediate major): iOS builds now need Xcode 26.4+ and min iOS 16.4.
Verification
expo-doctor20/20 ·expo prebuild --cleanwith all@generatedplugin injections intact (BGTask identifiers, AppDelegate bootstrap + background-session override, MainApplication init) ·expo run:iosandexpo run:androidbuild, launch and render with the native module reporting permission state on both platforms.🤖 Generated with Claude Code
https://claude.ai/code/session_012rn1KYa8uH8ikwK3AaHaLP