Open Closed

Expo version mismatch - can't use #10817


User avatar
0
jasenfici@gmail.com created

Hi,

Downloaded the latest version to try the new ReactNative tailwind mobile app development. Spun up project via AbpStudio.

React version running great in browser.
ReactNative version running great in browser.

I've never used Expo before but the docs were straight forward. Downloaded Expo to my iPhone, got the tunnelling up, launched the app and got my Expo QR code. Everything good.

However, when I try to connect I get this error on both the console and in Expo:

`› Scan the QR code above to open in Expo Go. › Metro: exp://192.168.4.21:19000 › Web: http://localhost:19000

› Using Expo Go (Press s to switch to development build) › Press ? │ show all commands

1 package may need updating. Run npx expo install --check for details. Logs for your project will appear below. Press Ctrl+C to exit. ERROR Project is incompatible with this version of Expo Go

The project you requested requires a newer version of Expo Go.

How to fix this error:

Download the latest version of Expo Go from the App Store.`

It looks like the ABP project uses Expo SDK 56, while the App Store version of Expo Go currently supports SDK 54. There's no real way for me to sync this that I know of..

Shouldn't I expect this to work out of the box?

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

3 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • This is an Expo Go limitation, not an ABP/ABP Studio runtime problem: Expo Go can only open projects whose Expo SDK version is supported by the Expo Go app version installed on your device. If your generated mobile app is on Expo SDK 56 while the App Store Expo Go you have only supports up to SDK 54, you’ll get exactly: “Project is incompatible with this version of Expo Go… requires a newer version of Expo Go.”

    • What you can do (practical options):

      1. Update Expo Go to a version that supports your project’s SDK (56).
        • If the App Store version hasn’t rolled out SDK 56 support yet in your region/device, you typically can’t force that immediately.
      2. Use a Development Build instead of Expo Go (recommended when Expo Go lags behind):
        • In the terminal running npx expo start, use the option shown by Expo: “Press s to switch to development build” and proceed with a dev build flow for iOS. This avoids the Expo Go SDK compatibility lockstep.
      3. Downgrade the project’s Expo SDK to the version supported by your Expo Go (e.g., 54).
        • This is possible, but it’s effectively changing the template dependencies and can cascade into other dependency/version changes. It’s generally not the best “out of the box” path.
    • Should it work out of the box?

      • It should work out of the box as long as Expo Go supports the SDK version used by the template. When Expo releases a new SDK, there can be a period where templates move forward and Expo Go on the App Store is still behind, and in that window the correct approach is to use a development build.

    Links (verified):

    • https://abp.io/docs/10.4/framework/ui/react-native/
    • https://abp.io/community/articles/rxjiyrpb

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    jasenfici@gmail.com created

    Hi,

    I appreciate the AI response but this is kind of a non-answer. If Abp is requiring Expo libraries that are versioned to Expo releases we don't have access to I don't see the solution for syncing them. Shouldn't Abp's out of the box solution run on what's generally available to Expo on ios?

    The only way I was able to get this to work was install Testflight, get ExpoGo beta installed, which is not v57, then spend an hour with ChatGPT trying to upgrade abp.io from 56 to 57. So first Abp uses 56 which is ahead of Expo main release, then it's behind the beta release. Bit of a nightmare honestly.

    thanks, jasen

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Hi,

    You're right, and this isn't something you did wrong. The React Native template currently uses Expo SDK 56, but the Expo Go app on the App Store is stuck at SDK 54 because Apple hasn't approved Expo's newer submissions for months. Expo explained the situation in this changelog post. Since iPhones can only install Expo Go from the App Store, an SDK 56 project can't be opened in Expo Go on a real device right now.

    Until this is sorted out on the template side, you can downgrade the generated app to SDK 54. In the react-native folder, run:

    npx expo install expo@^54.0.0
    npx expo install --fix
    yarn add react-native@0.81.5
    yarn add -D @types/react@~19.1.10 typescript@~5.9.2
    

    The separate react-native command is needed because the template excludes it from expo install --fix (see expo.install.exclude in package.json), so it has to be pinned manually. Also stick with yarn for this project (it ships a yarn.lock); npm install fails with a peer dependency conflict.

    After that, yarn start and scan the QR code again - the project will report SDK 54 to Expo Go, matching the version supported by the App Store build.

    We'll also review the Expo SDK version used by the template so this mismatch is handled on the template side as well.

    Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 24, 2026, 12:09
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.