Expo SDK 37 deprecates ExpoKit and removes UIWebView usage
Expo has released SDK 37.0.0, which uses React Native 0.61 internally. It is the first release under a new quarterly schedule: Expo plans further SDK versions in June, September, and December, so teams can plan their upgrade cycles more predictably.
ExpoKit deprecated in favor of the Bare workflow
With Updates, SplashScreen, and Notifications modules now available in the Bare workflow, Expo considers it at or beyond feature parity with ExpoKit, which is deprecated as of SDK 37. New projects should use the Bare workflow, and existing ExpoKit projects should migrate when possible. ExpoKit will still ship for SDK 37 and 38, but SDK 38 will be its last update. Apps already in the stores will keep running.
New Updates module
The new expo-updates module enables over-the-air updates in both Managed and Bare apps, and works with any server that implements the Expo protocol. import { Updates } from 'expo'; still works in SDK 37 but will be removed in SDK 38. API changes include:
Updates.fetchUpdateAsyncno longer accepts arguments.Updates.addListeneronly reports automatically downloaded updates, and event names have changed.Updates.reloadFromCacheis renamed toUpdates.reloadAsync, andUpdates.reloadis removed.
UIWebView removed
Apple will soon reject App Store submissions that use the deprecated UIWebView API. SDK 37 builds no longer depend on it, and the fix has been backported to the SDK 36 builders. To submit new iOS builds, projects need to be on SDK 36 or 37.
Firebase, dev menu and CLI
Firebase Analytics now works in the Managed workflow, using the native Firebase SDK in production and a JavaScript implementation in the Expo client. A helper package, expo-firebase-recaptcha, provides the building blocks for the reCAPTCHA verifier required by Firebase Phone Auth and is expected shortly after the release. The iOS and Android Expo clients get a redesigned dev menu. On the CLI, expo start --android tries to open an emulator, install the Expo client, and launch the project, while expo start --android --ios --web starts all platforms in parallel.
Expo Web
Web support for react-native-gesture-handler and react-native-reanimated has improved. expo start:web --https automatically signs SSL certificates, favicons are generated automatically, and the new expo-pwa CLI gives finer control over PWA assets. Several experimental expo.web config options were removed, most in favor of tags in web/index.html. Projects with @expo/webpack-config installed locally should upgrade it (currently 0.11.11). Web support for React Navigation v5 is still in progress.
Deprecations and upgrading
The experimental AR module will ship for the last time in SDK 37, and SDK 33 is no longer supported in the Expo client, although standalone SDK 33 apps keep working. Snack also received faster, more reliable web runtime updates.
To upgrade from SDK 36, run expo upgrade with the latest expo-cli (npm i -g expo-cli), update the Expo client app, and check the changelog for breaking changes. Standalone apps need a new build via expo build:ios or expo build:android.
Links
Source: web.archive.org