Skip to content

Expo SDK 35 adds iOS 13 Dark Mode and Apple Authentication

updated

Expo has released SDK v35.0.0. It stays on React Native 0.59.8, the same version used by SDKs 33 and 34. The release focuses on full iOS 13 support and also brings Expo Web improvements, several small new modules, and a handful of breaking changes.

iOS 13: Dark Mode and Sign in with Apple

SDK 35 includes react-native-appearance, which lets apps detect a user's appearance preference and adjust the UI to match. Expo does not provide UI primitives that switch to dark styles on their own, so each app has to implement its own dark theme. React Navigation users can turn on a built-in dark theme for navigation components.

The new AppleAuthentication module provides "Sign in with Apple" login and an AppleAuthenticationButton component. Apple now requires iOS apps that offer third-party logins such as Google or Facebook to also offer Apple Authentication, using Apple's own button, in order to pass App Store Review. Apps in that position need this module before they submit an iOS 13 update.

Expo Web and new modules

  • Server-side rendering: All Expo packages now support server-side rendering.
  • Deployment: Expo Web now integrates with Next.js and the ZEIT Now service.
  • Device and environment info: New modules Device, Application, Battery, Network and Cellular report details about the device, the app, power state and connectivity.
  • Bundled libraries: react-native-shared-element and react-native-safe-area-context are now included in the Expo client and in standalone/ExpoKit apps.
  • Lazy loading: babel-preset-expo gains a lazyImports option for lazy initialization and inline requires.

Branch support returns on Android

Managed projects built with SDK 34 and above can opt into Branch at build time. The steps are:

  1. Run expo install expo-branch.
  2. Set the API key under android.config.branch.apiKey in app.json.
  3. Make sure expo-branch is listed in package.json when you run expo build:android.

SDKs 31 and 32 dropped from the Expo client

SDK 33 was the first version with 64-bit support, and every SDK version in the Expo client on Google Play must have it, so SDKs 31 and 32 no longer run in the latest Expo client. Standalone apps built with those versions keep working, and expo build still accepts them for now. However, submitting an updated APK to Google Play requires upgrading to SDK 33 or later.

Breaking changes

  • Admob: Ads now require expo.[platform].config.googleMobileAdsAppId in app.json.
  • Contacts: The note field is removed on iOS.
  • Facebook: The underlying iOS library upgrade removed every login behavior other than browser, and the behavior parameter no longer has any effect.
  • Google: loginAsync now honors redirectUrl in the Expo Client.
  • Localization: The country constants are replaced by region, which is available only on iOS and Web.

Upgrading

  1. In app.json, set sdkVersion to "35.0.0".
  2. In package.json, update these dependencies:
    • expo to "^35.0.0"
    • react to "16.8.3"
    • react-native to "https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz"
  3. React Navigation users should run expo install react-native-gesture-handler react-native-reanimated, because these packages are no longer bundled in the expo package.
  4. Delete node_modules, reinstall dependencies, and run expo start -c.

Standalone apps need a new build with expo build:ios or expo build:android to pick up the new SDK version.

Source: web.archive.org