Repository navigation
chore(example): upgrade to Expo SDK 57 for Xcode 27 and iOS 27 - #68
Merged
Merged
Conversation
- Bump the example to Expo SDK 57 / React Native 0.86.3 and align the React Native tooling devDependencies and gradle-plugin resolution. - Opt in to the UIKit scene lifecycle with expo-build-properties ios.enableSceneSupport, which iOS 27 requires at launch. - Bump react-native-builder-bob to 0.43.2 so its babel-config handles Expo calling the Babel config without a filename. - Bump uniwind to 1.6.3+ to fix the Metro "Unexpectedly escaped traversal" invariant when the server root is the monorepo root.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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.
Summary
The example app (Expo SDK 55) doesn't work with Xcode 27. The build fails, and once you get past that, the app exits at launch on iOS 27 simulators with
UIScene life cycle is required for apps built with this SDK. This PR moves the example to Expo SDK 57 / React Native 0.86.3 and opts in to the scene lifecycle. Onlyexample/package.json,example/app.jsonandyarn.lockchange.ios/andandroid/are still generated by prebuild.CI still builds the example with Xcode 26. I haven't run it on that toolchain, so watch the
build-iosandbuild-androidjobs.expo-routerno longer pulls inexpo-image, so the SDWebImage pod with its 9.0 deployment target is gone. The app target is now at iOS 16.4, whichExpoRouter.podspecalso requires, so the iOS 16-only API in expo-router compiles. The@react-native/*and CLI devDependencies now match RN 0.86.3.expo-build-propertiesios.enableSceneSupport(Expo's SDK 57 instructions). With it, prebuild adds aUIApplicationSceneManifestthat usesEXExpoAppSceneDelegate. Remove this setting when moving to SDK 58, where the scene lifecycle is already on.react-native-builder-bob^0.43.2: SDK 57's Metro calls the Babel config without a filename, so bob 0.40'sgetConfigthrewConfiguration contains string/RegExp pattern, but no filename was passed to Babel. callstack/react-native-builder-bob@ca7bdc0 fixes it.uniwind^1.6.3: with 1.6.1, every bundle failed withUnexpectedly escaped traversalfrom@expo/metro-file-mapin this monorepo layout. This is MetroUnexpectedly escaped traversalinvariant innativeResolverduring Expo eager bundle聽uni-stack/uniwind#505, fixed by fix: use node resolver to prevent escaped traversal errors聽uni-stack/uniwind#506. The lockfile now resolves to 1.12.2.The root
package.jsonstays onreact-native0.83.0 for Jest/tsc.react-native-monorepo-configstill points the example's Metro at its own 0.86.3 copy.Test Plan
Ran from
example/, using a Debug simulator build fromexpo prebuild --clean:ease-example://<route>warm deep links, which also exercises URL forwarding through the scene delegate.frame-metricsmodule.expo start --web): the home screen and/bannerrender.