Skip to content

Expo SDK 34 fixes an iOS 13 crash and requires modular imports

updated

Expo has released SDK 34.0.0. It stays on React Native 0.59.8, the same version used by SDK 33. The team describes it mainly as a maintenance release focused on stability and infrastructure rather than new modules, and expects the next few SDK releases to follow the same pattern.

64-bit Android and App Bundles

SDK 34 supports 64-bit Android builds and Android App Bundles (AABs). Starting August 1st, Google Play requires 64-bit support for new app updates, so projects must be built with SDK 33 or 34 to keep shipping updates. AABs are optional, but they let Google serve device-specific APKs, which can shrink download size significantly. To build one, run expo build:android -t app-bundle on an SDK 33 or 34 project. No extra flag is needed for 64-bit.

iOS 13 crash fix

Apps built with React Native 0.59.8 or earlier, including every previous Expo SDK, crash on launch on the iOS 13 public beta. SDK 34 patches this crash. The fix has also been backported to the Turtle builders for SDK 31, 32 and 33, so running expo build:ios picks it up without upgrading. Expo recommends that production apps ship a new build before iOS 13 reaches the public in September.

Modular imports are now required

Importing most modules from the expo package, such as import { FileSystem } from 'expo';, now throws an error instead of a deprecation warning. Modules should be installed with expo install, which picks a version compatible with the SDK. For example, run expo install expo-file-system and then use import * as FileSystem from 'expo-file-system';.

The change prepares for tree-shaking and makes it easier to move between the managed and bare workflows. The expo-codemod utility can rewrite affected imports automatically. Dependencies that still use the old import style must be upgraded before a project can move to SDK 34.

Web, Snack and the bare workflow

Snack can now preview projects on web alongside Android and iOS, for SDK 33 or 34. Expo for web, still in beta, gains:

  • experimental support for react-native-gesture-handler
  • a universal jest config that works with all three platforms
  • increased babel stability and testing

For web routing, Expo currently suggests libraries such as react-router. The bare workflow template can now run inside the Expo client and on Expo for web.

API changes and breaking changes

  • ImagePicker can record video through launchCameraAsync.
  • LocalAuthentication adds a fallbackLabel option on iOS.
  • SplashScreen adds a native mode on Android.
  • FaceDetector now uses MLKit, which fixes compatibility with react-native-firebase.

Breaking changes:

  • Calendar drops the DEFAULT constant. Pass null to use the default calendar instead.
  • LocalAuthentication: the iOS-only string argument to authenticateAsync is replaced by an object with a promptMessage key.

Projects using react-navigation should run expo install react-native-gesture-handler react-native-reanimated, because these are no longer bundled in the expo package.

Looking ahead

Expo plans:

  • an SDK with full Xcode 11 and iOS 13 support around the public iOS 13 launch
  • work toward Hermes support
  • deprecating ExpoKit in favor of the bare workflow once OTA updates and push notifications work there

SDK 31 and 32 will be dropped when SDK 35 ships.

Source: web.archive.org