Expo SDK 39 adds React Native 0.63 and iOS 14 support
Expo has released SDK 39, its third release of 2020. The update touches the SDK itself, the Expo development clients, Expo CLI, the documentation and Snack.
Platform support
SDK 39 is fully compatible with iOS 14 and moves to React Native 0.63, which brings LogBox, the Pressable component and support for Native Colors. On the web side, it jumps from React Native for Web v11 to v13, which uses React 16.13.1 and should remove lifecycle-method warnings developers had been seeing.
New SDK features
- Interactive notifications:
expo-notificationsnow supports notification categories, letting users act on a notification without opening the app. The library now covers everything the legacy Notifications module did; that legacy module remains in SDK 39 but will be removed in the near future. - QR scanning on web via
expo-camera. - Google sign-in built into
expo-auth-session, usinguseAuthRequestfromexpo-auth-session/providers/google. - Screenshot listener:
ScreenCapture.addScreenshotListenerlets apps react when a user takes a screenshot. - Synchronous random bytes:
Random.getRandomBytes()inexpo-randomenables polyfills such asreact-native-get-random-values, making packages likeuuidusable in managed apps. - Experimental
react-native-reanimatedv2 alpha support, which requires opt-in configuration. A preconfigured project can be created withnpx crna --template with-reanimated2.
The expo-updates and expo-splash-screen unimodules are now part of the managed workflow. Projects that import Updates or SplashScreen from the expo package must install the individual packages. Updates configuration in app.json is now applied at build time rather than at runtime. Dark mode splash screens are not yet supported in the managed workflow.
Development clients and CLI
Projects now always load synchronously in the Expo client, so the latest version is shown during development. A new indicator on the loading screen can be removed in the Expo client by publishing with "developmentClient": { "silentLaunch": true }. The client also gains a project details screen, password autofill and SDK version visibility.
Expo CLI adds Personal Access Tokens for CI and scripts, device selection after expo start (shift+i for iOS simulators, shift+a for Android devices), Apple Keychain support (disable with EXPO_NO_KEYCHAIN=true), bundle size stats on expo publish, a redesigned expo --help, and a public-url prompt for expo export. Running eject now applies nearly all app.json / app.config.js config to native projects, with iCloud entitlements the only exception.
Other changes
An internal bug bash in July addressed over 420 issues, with notable fixes to expo-av, including more reliable iOS background audio, plus a full audit of how Expo handles native Android permissions and updated permissions documentation. Snack now lints all TypeScript and JavaScript files. Service workers on web are now opt-in in Expo's Webpack config.
SDK 35 is no longer supported in the latest Expo client, and SDK 36 support is planned to be dropped with the next release, expected in December.
Upgrading
Managed projects can run expo upgrade with the latest expo-cli (npm i -g expo-cli), then rebuild standalone apps with expo build:ios and expo build:android. Bare projects also need to apply the native changes for React Native 0.63, then run npx pod-install. Expo notes known development client issues related to a SplashScreen warning and reloading by pressing 'r' twice.
Links
Source: web.archive.org