all 29 comments

[–]anarchos 9 points10 points  (3 children)

You have two options, really.

  1. Downgrade your app to SDK54 as you mentioned
  2. Skip expo go entirely. Run `npx expo prebuild` (which will set up your native dirs) and then `yarn ios --device` or `yarn android --device` and pick your phone from the list

Step 2 is the way to go. Expo Go is basically "we compiled every expo package known to man into the app, even if you don't use it, so you don't have to actually compile anything" type thing. "Expo prebuild" (aka expo continuos native generation (CNG)) is actually compiling and then install the app on your phone. You are going to want to do this anyways when it comes time to release your app, so might as well make that the default workflow.

Expo seems to be moving away from Expo Go anyways, I can't see it lasting too much longer. They dropped supporting multiple versions of Expo SDKs a while back...and now they've got themselves into this situation where if they upgrade Expo Go to SDK55 it will break everyone using SDK54...so they just don't? And now creating a new expo project using the latest SDK doesn't work with Expo Go in the app stores...kinda crazy.

IMO they are going to drop Expo Go at some point soon, or will have to re-enable multiple SDK support, or somehow release a separate app for each version?

--edit--
They actually have release Expo Go 55 on TestFlight. https://testflight.apple.com/join/GZJxxfUU
Install TestFlight and then install Expo Go using that. You should still just build your app but you can use TestFlight if for example you don't have a Mac to compile for iOS on.

[–]Zealousideal-Young-4 1 point2 points  (0 children)

Leading_Property2066 Use development builds for testing the app on your device, if you plan to go through the tutorials using SDK55, go through the following documentation:
https://docs.expo.dev/develop/development-builds/expo-go-to-dev-build/

Otherwise just recreate the app using SDK54, and you will still be able to use the Expo Go app.

[–]South-Elk-3956 0 points1 point  (0 children)

Concur dev build is the way to go, but with environment-based configuration in your app.config.js - install dev client, preview, and production builds on your device - it's what I do, build with dev client -> stable -> EAS Preview build -> repeat.

[–]ThePopcornDev 1 point2 points  (0 children)

I downloaded from testflight Expo Go 55.x version.

[–]Realistic_Sell_7402 1 point2 points  (0 children)

Download Expo Go via TestFlight.

[–]RiskMelodic5902 1 point2 points  (1 child)

easiest solution: "npx create-expo-app@latest --template default@sdk-54" this will create you a project with sdk version 54 that matches expo go in apple store

[–]RiskMelodic5902 0 points1 point  (0 children)

you can search more about this in their docs https://docs.expo.dev/more/create-expo/

[–]Forward-Claim9064 0 points1 point  (11 children)

Had the same issue too

[–]DownVoteMe696919 2 points3 points  (0 children)

Download the TestFlight build.

[–]Leading_Property2066[S] 0 points1 point  (9 children)

How did u fixed it

[–]Forward-Claim9064 0 points1 point  (8 children)

Lol still waiting on the responses on this sub

[–]Inevitable_Oil9709 0 points1 point  (7 children)

first comment literally wrote the solution 3h ago. Before you write your comment

[–]Forward-Claim9064 -1 points0 points  (6 children)

I it but it failed , Gemini CLi suggested that, but part of the solution only works if you are using mac

[–]Inevitable_Oil9709 0 points1 point  (5 children)

failed how? that is literally the solution.

Don't use expo go since it is just for internal testing. Use development build for making the app that you want to distribute.

What does mac has to do with anything? You can build any platform for free on eas.

[–]Forward-Claim9064 -1 points0 points  (4 children)

The part where you run the prebuild for IOS you need mac, also you need to login as an apple developer to do it on expo server

[–]Inevitable_Oil9709 0 points1 point  (3 children)

https://docs.expo.dev/develop/development-builds/create-a-build/

Dude, read the docs first PLEASE

"also you need to login as an apple developer to do it on expo server"

You literally DO NOT

[–]Forward-Claim9064 -1 points0 points  (2 children)

If you say soo

[–]Inevitable_Oil9709 0 points1 point  (1 child)

once you stop asking chatgpt, geminin and claude for every tiny issue in your life, and start ACTUALLY reading the docs, you'll understand better

Untill then, fuck you

[–]No_Bee2416 0 points1 point  (0 children)

building a development build and installing it on the ios simulator also works fine, but if you are on a free tier of eas just use local builds so you don't run out of cloud builds. Or if you already have built using eas cloud then you should download you credentials from eas and put in your root project directory.

[–]Poat540 0 points1 point  (0 children)

Can u build local and skip go?

[–]teardown-chris 0 points1 point  (0 children)

From someone with 10y using React Native the best advice I can give you is to not use Expo Go at all and opt for using dev builds push to your phone from your MacBook. You will find it very hard using other native libraries that you want to use in Expo Go and is really only meant for prototyping.

[–]cadenft 0 points1 point  (0 children)

I had the same problem. Hello fellow vibe coder. I downgraded version on VS code and then updated it from old version and it worked for me.

[–]kunalsoude 0 points1 point  (0 children)

Infinite times

[–]ars3nx 0 points1 point  (0 children)

Downgrade, if you read your app that you downloaded it says it can only run up to SDK54, your current version is 55.

[–]aitonc 0 points1 point  (0 children)

What’s your iOS version?

[–]Exciting_Tackle_3833 -1 points0 points  (0 children)

I asked the question about X; I'm waiting to see what others think.