Ejected App Not loading the requested app (30.0.0)


#1

Created a new expo project in 30.0.0.
Prepped app.json
Ejected
cd ios
pod install
expo start
hit run in expo

“There was a problem loading the requested app. It looks liek you may be using a LAN URL. Make sure your device is on the same network as the server or try using a tunnel.”

And the url on the simulator is the same as the “Your app is running at …” url. “exp05baeabc46d3409da7e269233fb2b513://192.168.86.30:19000”

I have really run out of ideas how to get the standalone app to see the locally running process.


#2

Same here,
hope someone have a solution


#3

Just a note that I’m having this exact same issue and posted about it here: Detached app seems to be loading from the wrong local address


#4

Thanks posting. It seems like an expo problem. Hoping to get some assistance today. Going to hop on the Slack and see if I can get this some attention.


#5

same problem;

  • i created a really plain empty project with sdk30
  • eject
  • expo start
  • cd ios; pod install
  • open in xcode
  • start in ios simulator with pressing the button inside xcode “build and then run the current scheme”
  • on ios simulator the app starts, shows the splash-screen and then the error message “there was a problem loading the requested app…”

#6

Sorry for this inconvenience :disappointed: We’ve just published ExpoKit v2.8.2 for ejected apps that should fix this issue, so you can try to update it in your Podfiles or just create a new app using expo init and then expo eject. Let me know if you have any questions :wink:


Detached app seems to be loading from the wrong local address
#7

Hey!

Thanks so much for your hard work and I really appreciate the response!

I updated to 2.8.2 in the Podfile, cleared out my Pods, cleaned my project in XCode and rebuilt. However, I am still getting the same error when running the app.

Here’s what I’m running to launch expo:

Here’s what I’m getting when the app runs:

It seems like now it is loading the proper URL, but for some reason just not connecting.

Thanks again!


#8

Hey,

Looks like it solved the same problem for other users - see an issue on GitHub.
Could you try running Expo with --lan flag? It might be a problem with a tunnel :thinking:


#9

Hm, dang!

I tried with --lan but still no go. Is there any other way to test the tunnel to verify if the issue is the tunnel or the app?

When I connect with --lan, how does the app know to use the lan URL? (It is still trying to connect through 9p-vpr.nickyhajal.mobile.exp.direct)


#10

for me now everything is solved and working with creating a brand new expo-app:

expo init -t blank testsdk30
# after that it uses "expo": "^30.0.1",

I had some small issues after ejecting. But it could be solved by reinstalling modules:

rm -Rf ./node_modules
yarn

…then it worked

thanks to the expo-developers


#11

Hey Anil, could it be an issue with almost empty node_modules/react-native directory? It is the reason of errors in pod install as some RN podspecs cannot be found.
I encountered this problem as well and another workaround is to simply do yarn between expo init and expo eject.


#12

Just wanted to come back and say thank you for the hard work ExpoTeam. After updating npm global expo-cli and exp and creating a brand new expo app everything seems to be working as expected.


#13

@tsapeta yes exactly; to verify - I again created a brand new project;
AFTER expo eject is finished the folder node_modules/react-native contains only the subfolder
node_modules/.bin which contains 6 symlinks

so when I do expo start I get the message
Error: React native is not installed. Please run `npm install` in your project directory

the solution --> as you described
:grinning::tada: