Skip to content

Expo SDK 47 ships Expo Modules API 1.0 and React Native 0.70.5

updated

Expo has released SDK 47, which is built on React Native 0.70.5 and React 18.1.0. The release stabilizes Expo's tooling for writing native modules, expands Hermes support, and removes several legacy features.

Expo Modules API 1.0

The headline change is the first stable release of the Expo Modules API. It is aimed at library authors building native code for Expo and React Native apps, treats Swift and Kotlin as first-class languages, and is built on JSI. According to Expo, modules created with it support Fabric (the New Architecture) without requiring any C++. A new module can be scaffolded with:

npx create-expo-module@latest

Hermes in Expo Go and debugging

Hermes is now available in Expo Go for iOS. The Hermes inspector can be opened from the development menu in both Expo Go and development builds, so developers can use the same debugger exposed through Flipper without installing the Flipper SDK or desktop app. "Open JS Debugger" launches the inspector in Chrome DevTools, and unlike remote debugging with JSC, it works with JSI. Expo plans to make Hermes the default in SDK 48 and encourages teams to migrate during SDK 47. The bundled Hermes version also now supports the Intl API.

Experimental Fabric support

expo-av, expo-camera and expo-linear-gradient now support Fabric. View-based modules still lacking support are expo-apple-authentication, expo-barcode-scanner, expo-blur and expo-gl, with work ongoing for expo-dev-client. There is no official way yet to enable Fabric in managed projects, and Expo advises against doing so via a config plugin for now.

Expo Router and config plugins

The beta of Expo Router, a file system-based routing API built on React Navigation, works with SDK 47 from expo-router@0.0.35 onward. Config plugin authors can now import from expo/config-plugins and expo/config, which are re-exported by the expo package, removing the need to bump @expo/config-plugins with each release.

EAS Update

expo-updates adds Updates.readLogEntriesAsync() for reading logs of events such as JS_RUNTIME_ERROR and NO_UPDATES_AVAILABLE, and updates can now be loaded in debug builds.

Breaking changes and removals

  • React Native Maps moves from 0.31.1 to 1.3.2, a major version bump.
  • expo-firebase-analytics and expo-firebase-recaptcha are deprecated in favor of React Native Firebase.
  • The app.json fields useNextNotificationsApi, android.googleSignIn, ios.merchantId, ios.googleSignIn, ios.splash.xib and appKey are no longer valid.
  • Classic builds (expo build:[ios|android]) are not supported; projects should use EAS Build or build locally after running prebuild. The Classic Build service ends at the close of 2022.
  • iOS 13.0 is now the minimum supported version.
  • SDK 44 is dropped from Expo Go, and SDK 45 will be dropped in the next release.

Expo is also inviting more developers into a private preview of M1 workers on EAS Build.

Upgrading

Managed projects should install expo-cli@6.0.0 or newer with npm i -g expo-cli, run expo-cli upgrade, then expo-cli doctor, and start the project with npx expo start. Bare projects additionally need Xcode 14.0 or newer, an iOS deployment target of 13.0 in build settings and the Podfile, and any relevant changes from the React Native Upgrade Helper. Development clients and standalone apps need fresh builds.

Source: web.archive.org