File: v54.0.0.md | Updated: 11/15/2025
Hide navigation
Search
Ctrl K
Home Guides EAS Reference Learn
Reference version
SDK 54
Archive Expo Snack Discord and Forums Newsletter
Copy page
Copy page
The Expo SDK provides access to device and system functionality such as contacts, camera, gyroscope, GPS location, and so on, in the form of packages. You can install any Expo SDK package using the npx expo install command. For example, three different packages are installed using the following command:
Terminal
Copy
- npx expo install expo-camera expo-contacts expo-sensors
After installing one or more packages, you can import them into your JavaScript code:
import { CameraView } from 'expo-camera'; import * as Contacts from 'expo-contacts'; import { Gyroscope } from 'expo-sensors';
This allows you to write Contacts.getContactsAsync()
and read the contacts from the device, read the gyroscope sensor to detect device movement, or start the phone's camera and take photos.
All Expo SDK packages work in any React Native app
Expo apps are React Native apps, so all Expo SDK packages work in any React Native app with the expo package installed and configured. The easiest way to create a React Native app with support for Expo SDK packages is to use create-expo-app. However, you can also add Expo SDK support to an existing React Native app with the npx install-expo-modules command.
Terminal
Copy
# Create a project named my-app
- npx create-expo-app my-app --template bare-minimum
Install Expo SDK packages in existing React Native apps
Learn more about configuring projects created with npx @react-native-community/cli@latest init to Expo SDK packages.
Use libraries
Learn how to install Expo SDK packages in your project.
New Expo SDK versions are released three times each year. Between these releases, we publish pre-release versions of the expo package and all of the Expo SDK packages. Pre-releases are not considered stable and should only be used if you are comfortable with the risk of encountering bugs or other issues.
Canary releases represent a snapshot of the state of the main branch at the time they are published. Canary package versions include -canary in the name, along with the date and commit hash, such as 54.0.0-canary-20240418-8d74597. To install the latest canary release:
Terminal
Copy
# Install the alpha version of expo and its related packages
- npm install expo@canary && npx expo install --fix
You can often use pre-release versions of individual packages with stable releases of the Expo SDK. There may occasionally be incompatibilities or other issues that arise in canary-quality releases. You may want to silence dependency validation warnings if you opt in to the canary package and once you have verified that it works well for your use cases.
Before each Expo SDK release, we publish beta versions of the expo package and all of the Expo SDK packages. Beta releases are considered much more stable than canary releases, and we encourage developers to try them out on their apps and share their feedback. Beta releases use the beta tag on npm and follow the instructions in the related changelog
post.
Each Expo SDK version depends on a React Native version
| Expo SDK version | React Native version | React version | React Native Web version | React Native TV version | Minimum Node.js version | | --- | --- | --- | --- | --- | --- | | 54.0.0 | 0.81 | 19.1.0 | 0.21.0 | 0.81-stable | 20.19.x | | 53.0.0 | 0.79 | 19.0.0 | 0.20.0 | 0.79-stable | 20.18.x | | 52.0.0 | 0.76 | 18.3.1 | 0.19.13 | 0.77-stable | 20.18.x |
Expo SDK policy for tracking React Native releases
Why not release a new Expo SDK version immediately for every React Native release?
At Expo, we have found that releasing three major version provides a good balance of stability and innovation for developers depending on our open source tools. Expo and Meta work closely together on releases, and we will keep improving our processes to get the latest Expo and React Native features to you as quickly as possible.
What if I need a change from the latest React Native version and it's not yet in an Expo SDK release?
We work closely with the team at Meta to ensure that any urgent fixes are included in the React Native version used by the latest Expo SDK. If your issue won't be cherrypicked into an existing release because it is more niche, or it involves a breaking change, then you have two options:
patch-package
to pull in the fix.Can I use an older version of React Native with the latest Expo SDK?
Packages in the Expo SDK are intended to support the target React Native version for that SDK. Typically, they will not support older versions of React Native, but they may. When a new version of React Native is released, the latest versions of the Expo SDK packages are typically updated to support it. However, this may take weeks or more, depending on the extent of the changes in the release.
Support for Android and iOS versions
Each version of Expo SDK supports a minimum OS version of Android and iOS. For Android, the compileSdkVersion is defined which tells the Gradle
which Android SDK version to use to compile the app. This also means that you can use the Android API features included in that SDK version and from the previous versions. For iOS, the Xcode
tells the minimum Xcode SDK version to use to compile the app.
| Expo SDK version | Android version | compileSdkVersion | targetSdkVersion | iOS version | Xcode version |
| --- | --- | --- | --- | --- | --- |
| 54.0.0 | 7+ | 36 | 36 | 15.1+ | 16.1+ |
| 53.0.0 | 7+ | 35 | 35 | 15.1+ | 16.0+ |
| 52.0.0 | 7+ | 35 | 34 | 15.1+ | 16.0+ |
When deciding whether to upgrade your Expo SDK version, consider both Expo's SDK version and app store submission requirements, as described in the above table. Google Play Store and Apple App Store periodically increase their minimum required OS versions and API levels, which are required for new app submissions. Expo has no control over the app store requirements, and you should check Google and Apple for the current store submission requirements.