概要
公開日: 2026-05-22
翻訳生成に失敗したため、原文をそのまま保存しています。
原文
Expo SDK 56 is here, with support for React Native 0.85, and React 19.2. Android API level 36 and Xcode 26.4 and higher are supported. Also unchanged are the minimum supported operating systems: SDK 56 can build apps for Android 7+ and iOS 16.4 and higher. Check out the changelog to get a full picture of all that’s included. And here’s a short highlight video: Each SDK undergoes extensive testing and a beta test period, where the Expo team and the community collaborate to find issues that might stand in the way of a fast and smooth upgrade for others. A lot of Expo engineers maintain our own apps and try to upgrade those as soon as the beta is out. Nonetheless, there’s practically infinite possibilities out there. Every app is unique, and has its own complexities that will need to be accounted for when upgrading. Therefore, we wanted to highlight some specific key changes that may affect your upgrade to SDK 56, as well as some evergreen advice when it comes to upgrading to the latest Expo SDK. Key things to know as you upgrade to SDK 56 Power your SDK upgrade with Claude Code At Expo, we use Claude Code in our day-to-day work. Based on our experiences, we’ve published some skills to help with common tasks within Expo apps in the expo/skills library. One of these skills is for upgrading to the latest Expo SDK version. In addition to the basics like updating package versions, it handles things like breaking changes, cleaning up outdated configurations, and more. Within Claude Code on your terminal, run /plugin marketplace add expo/skills to add the skills marketplace to Claude, and then /plugin install expo After restarting Claude, you can ask it in plain language to upgrade your SDK. If it’s installed correctly, you should see Claude reference the skill as it gets started: Claude prompt showing usage of Expo upgrade skill You can also import Expo skills into other agents via bunx skills add expo/skills As always, do your work on a separate branch, and review your code before merge and deploy. LLMs are amazing, but Claude and the Expo upgrade skill can’t be aware of every possible scenario. Human developers are a vital part of this workflow! Faster native builds To speed up iOS builds, SDK 56 ships prebuilt XCFrameworks for our most complex Expo modules on iOS. This is enabled by default both locally and on EAS Build — no configuration required. To opt out, set the EXPO_USE_PRECOMPILED_MODULES environment variable to 0 (for local builds), and also as an EAS environment variable (for EAS Build). For Android, a new opt-in android.usePrecompiledHeaders option in expo-build-properties applies CMake precompiled headers to the C++ codegen output for every autolinked native module, dramatically cutting CMake compile times on Android. Expo Go update Expo Go for SDK 56 is not available on the Apple App Store or Google Play Store. We do not have a timeline for when they will be, and we will update the SDK 56 changelog when we have more news to share. For more information, you can refer to “Expo Go and the App Store in May 2026.” The Expo Go app is our tool for getting started quickly, it's an educational tool to help you learn to build on mobile. We encourage you to take advantage of this transition period to migrate your project to using a development build, which provides you with everything that you need to build an app that you ship to stores. You can install Expo Go for SDK 56 from Expo CLI directly on Android devices. For iOS, you can use the TestFlight External Beta or the eas go command to create an Expo Go build for SDK 56 and upload it to your own TestFlight team. Hermes bytecode diffing for updates is enabled by default In SDK 55 we introduced opt-in Hermes bytecode diffing for expo-updates and EAS Update: instead of downloading a full bundle on every update, the client downloads a binary patch against the previously installed bytecode. Diffing is on by default in SDK 56. To opt out, set "enableBsdiffPatchSupport": false in the