Skip to content

Expo SDK 36 ships with React Native 0.61 and Fast Refresh

updated

Expo has released SDK 36.0.0, a maintenance release built on React Native 0.61.4. Even without flashy new features, it brings many bugfixes, consistency improvements and quality-of-life changes, along with Expo's 2020 plans for the Bare workflow and ExpoKit.

React Native 0.61

By moving to React Native 0.61, SDK 36 brings in many changes from the 0.60 and 0.61 releases. These include Fast Refresh, which combines the best of Live Reload and Hot Reload, accessibility improvements on Android and iOS, and React 16.9 with Profiler, testing improvements and deprecated lifecycle method names.

Dark Mode on Android and Web

SDK 35 added iOS Dark Mode support through react-native-appearance. That module now also works on Android and Web, so apps can listen to the user's appearance preference and adjust their UI. React Navigation users can enable a built-in dark theme for navigation components.

Permissions moved into modules

Previously, every permission request went through expo-permissions. Now each module that needs user-facing permissions exposes its own methods for requesting and checking them, for example MediaLibrary.requestPermissionsAsync(). The Permissions module remains available for backwards compatibility.

Bug hunt

During October and November, the Expo team closed over 350 issues across the expo and expo-cli repositories, with the fixes listed in the changelog. Library updates and breaking changes are now also documented in the changelog instead of the release notes.

Notable API changes

  • Facebook: to avoid unintended data collection, the Facebook module no longer auto-initializes. Apps using Facebook login must initialize the SDK manually, at runtime or via an app.json setting, before calling logInWithReadPermissionsAsync.
  • ErrorRecovery: now extracted to the expo-error-recovery unimodule, so imports need updating. It can now be used in Bare workflow projects.
  • Web: more Permissions types and expanded Camera functionality and browser support. The docs now show Platform Compatibility for each module, and web support can be tried in a new project with expo start --web.
  • Android FileSystem: upgrading should resolve migration problems with FileSystem.documentDirectory in standalone apps reported in issue #4537.

ExpoKit and the Bare workflow

Expo considers the Bare workflow, which lets any React Native app use Expo APIs, the best path for apps that need more customization than the Managed workflow allows. Almost all of Expo's 60+ modules have been extracted into unimodules. Some ExpoKit features, such as Updates, SplashScreen and TaskManager, are not yet supported in Bare, but Expo expects to introduce solutions for the Bare workflow in 2020 and then phase out ExpoKit. ExpoKit support is unchanged for now, but developers considering ejecting to ExpoKit in new projects are advised to evaluate the alternatives first.

TLS reminder

From January 13, 2020, Expo's servers will require TLS 1.2 or 1.3. Teams whose servers send push notifications, publish updates or start builds through Expo should confirm they support TLS 1.2.

Upgrading

With the latest expo-cli (npm i -g expo-cli), run expo upgrade in the project directory and review the changelog's breaking changes. Update the Expo client on devices, or use expo client:install:ios and expo client:install:android for simulators. Standalone apps need a new build with expo build:ios and/or expo build:android. Expo recommends testing standalone app upgrades before releasing them to production.

Source: web.archive.org