Skip to content

Expo SDK 53 ships React Native 0.79 with the New Architecture on by default

updated

Expo has released SDK 53, which includes React Native 0.79, React 19, and React Native Web 0.20.0. The release changes several defaults that affect both new and existing projects.

New Architecture on by default

The New Architecture is now enabled by default in all SDK 53 projects, with an opt-out for teams that are not ready. According to Expo, 74.6% of SDK 52 projects built on EAS Build in April 2025 already had it enabled. Opting out can be used to upgrade the SDK and switch architectures as separate steps.

Edge-to-edge on Android

With Android 16 removing the ability to opt out of edge-to-edge, Expo is rolling it out via react-native-edge-to-edge. It is enabled with no opt-out in Expo Go, enabled by default in new projects, and disabled (but encouraged) in existing projects. SDK 54 is expected to make it the default for all projects. New native Android projects also now use the DayNight theme.

Metro package exports

In React Native 0.79, Metro enables package.json exports support by default. Some libraries, including @supabase/supabase-js and @firebase/* packages, have known issues; developers can opt out with unstable_enablePackageExports: false. Expo recommends Expo Atlas, now stable and enabled with EXPO_ATLAS=1 npx expo, for spotting problems such as the dual package hazard.

New and updated modules

  • expo-background-task replaces expo-background-fetch, using WorkManager on Android and BGTaskScheduler on iOS.
  • expo-audio is now stable and recommended over expo-av, which will not receive new versions for SDK 54 and beyond.
  • expo-maps is in alpha, wrapping Google Maps on Android and Apple Maps on iOS, and requires iOS 17.
  • expo-sqlite gains experimental web support and libSQL support.
  • expo-updates adds Updates.setUpdateURLAndRequestHeadersOverride() and no longer copies embedded assets on Android launch, which reduced the updates startup step from about 300ms to 100ms in Expo's test project.

Tooling and builds

Precompiled Expo Modules can cut local Android build times by up to 25%. Development builds can now be distributed via TestFlight using npx testflight --profile development. An experimental experiments.remoteBuildCache option lets teams reuse builds that match a fingerprint. Expo Router adds build-time redirects and rewrites, guarded groups, and route prefetching. React Server Functions support is now in beta.

Breaking changes and deprecations

The iOS AppDelegate has moved from Objective-C to Swift, so config plugins that modify it need updating. The jsEngine field is deprecated as JavaScriptCore moves to @react-native-community/javascriptcore. Push notifications are no longer supported in Expo Go for Android, the setImmediate polyfill is removed, and the Android package name is no longer added automatically as a linking scheme. EAS Build now uses frozen lockfiles by default. Expo recommends Node 20 or later and Xcode 16.2+.

Developers may need overrides or resolutions to avoid multiple React installations caused by libraries with React 18 peer dependencies. Snack does not yet support SDK 53.

Source: expo.dev