Short answer
Check the expo version in package.json, then install the Expo Go build for that SDK from expo.dev/go on Android or the iOS Simulator. On a physical iPhone, the App Store has Expo Go up to SDK 54; SDK 55 and later need eas go through TestFlight. For an app you plan to ship, Expo recommends a development build instead of Expo Go.
Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
Why Expo Go refuses the project, and the fix
01
The project and Expo Go are on different SDKs
“Each build of Expo Go includes one Expo SDK version.” Expo, Expo Go version mismatch
Each Expo Go build runs one SDK version, set in your project by the expo package in package.json. An app made by an AI builder or a template can be on a newer or older SDK than the Expo Go on your phone.
02
The App Store doesn’t have Expo Go for your SDK
“Expo Go on the Apple App Store stops at SDK 54, and SDK 55 and later are not available there.” Expo, Expo Go version mismatch
The App Store version stops at SDK 54, so a project on SDK 54 can use it. For SDK 55 and later, build Expo Go with eas go and install it through TestFlight, which needs an Apple Developer Program membership. For SDK 53 or earlier, an older Expo Go can’t be installed on an iPhone: upgrade the project, or test on Android, the iOS Simulator or a development build. For an app you’ll ship, Simon would go straight to a development build.
03
Android or the simulator has the wrong Expo Go
“Visit expo.dev/go, select the SDK version used by your project and your target platform, then install the compatible Expo Go build.” Expo, Expo Go version mismatch
Install the matching build, then restart the development server with npx expo start and open the project again.
04
The project’s versions disagree with each other
“If your app config contains an sdkVersion field, remove it or make sure that it matches the expo dependency.” Expo, Expo Go version mismatch
If the error stays after installing the right Expo Go, an old sdkVersion in the app config or mismatched packages can be the cause. Check the config, then let Expo check and align the packages.
npx expo-doctor@latest npx expo install --fix05
Cannot find native module: the library isn’t in Expo Go
“A development build is essentially your own version of Expo Go where you are free to use any native libraries and change any native configuration.” Expo, Introduction to development builds
An error such as Cannot find native module ‘ExpoSomething’ means the code calls a library with native code that this Expo Go doesn’t include. Make a development build with npx expo install expo-dev-client and npx expo run:android or run:ios, or EAS Build, and open the project in it instead of Expo Go. run:ios needs a Mac with Xcode; with EAS, use a profile that builds the development client.
npx expo install expo-dev-client npx expo run:android eas build --profile development06
You’d rather move the project to a newer SDK
“We recommend upgrading SDK versions incrementally, one at a time.” Expo, Upgrade Expo SDK
Upgrading the project is the other way out. Expo recommends one SDK version at a time, so a breakage is easy to trace. Replace 58 with the SDK you are moving to.
npm install expo@^58.0.0 npx expo install --fix npx expo-doctor
Checked against the vendor’s docs on : Expo docs: Expo Go version mismatch; Expo docs: Introduction to development builds; Expo docs: Upgrade Expo SDK.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
- from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start
“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
Related: Expo app crashes in production · Expo EAS build failed · Expo and React Native unable to resolve module · Expo native module cannot be null