📄 expo/workflow/upgrading-expo-sdk-walkthrough

File: upgrading-expo-sdk-walkthrough.md | Updated: 11/15/2025

Source: https://docs.expo.dev/workflow/upgrading-expo-sdk-walkthrough

Hide navigation

Search

Ctrl K

Home Guides EAS Reference Learn

Archive Expo Snack Discord and Forums Newsletter

Upgrade Expo SDK

Edit page

Copy page

Learn how to incrementally upgrade the Expo SDK version in your project.

Edit page

Copy page

We recommend upgrading SDK versions incrementally, one at a time. Doing so will help you pinpoint breakages and issues that arise during the upgrade process.

With a new SDK release, the latest version enters the current release status. This applies to Expo Go as it only supports the latest SDK version and previous versions are no longer supported. We recommend using development builds for production apps as the backwards compatibility for older SDK versions on EAS services tends to be much longer, but not forever.

If you are looking to install a specific version of Expo Go, visit expo.dev/go . It supports downloads for Android devices/emulators and iOS simulators. However, due to iOS platform restrictions, only the latest version of Expo Go is available for installation on physical iOS devices.

How to upgrade to the latest SDK version

1

Upgrade the Expo SDK

Install the new version of the Expo package:

npm

Yarn

pnpm

Bun

Terminal

Copy

- npm install expo@^54.0.0

Terminal

Copy

- yarn add expo@^54.0.0

Terminal

Copy

- pnpm add expo@^54.0.0

Terminal

Copy

- bun install expo@^54.0.0

Depending on which SDK you're upgrading to, substitute the expo@^54.0.0 with the version range of the Expo SDK version you're targeting. For example, expo@^54.0.0 stands for SDK 54.

2

Upgrade dependencies

Upgrade all dependencies to match the installed SDK version. Then run expo-doctor command to check for common problems.

Terminal

Copy

- npx expo install --fix

- npx expo-doctor

3

Update native projects

  • If you use Continuous Native Generation : Delete the android and ios directories if you generated them for a previous SDK version in your local project directory. They'll be re-generated next time you run a build, either with npx expo run:ios, npx expo prebuild, or with EAS Build.
  • If you don't use Continuous Native Generation : Run npx pod-install if you have an ios directory. Apply any relevant changes from the Native project upgrade helper . Alternatively, you could consider adopting prebuild for easier upgrades in the future.

4

Follow the release notes for any other instructions

Read the SDK changelogs for the SDK version you are upgrading to. They contain important information about breaking changes, deprecations, and other changes that may affect your app. Refer to the "Upgrading your app" section at the bottom of the release notes page for any additional instructions.

SDK Changelogs

Each SDK announcement release notes post contains information deprecations, breaking changes, and anything else that might be unique to that particular SDK version. When upgrading, be sure to check these out to make sure you don't miss anything.

Deprecated SDK Version Changelogs

The following blog posts may included outdated information, but they are still useful for reference if you happen to fall far behind on SDK upgrades.

See a full list of deprecated SDK release changelogs