IOS Simulator hangs installing expo

I have the following configured and installed

Brew
Watchman
Xcode

  • simulator 12.2

npm

  • react native
  • expo-cli

I am trying to work on a previous project after resetting my machine. When I run expo to start with IOS simulator the following runs in my terminal then hangs:

Trying to open the project in iOS simulator…
Downloading the latest version of Expo client app
Installing Expo client on iOS simulator
/

I have tried manually installing expo but it still tries to install the client app through the terminal when I run the IOS simulator. Has anyone else run into this issue?

Hey @e3br,

What commands are you running? Also, can you provide the version numbers for your environment?

Cheers,
Adam

Versions
OSX Mojave 10.14.5
Node - 12.4.0
NPM - 6.9.0
Shell - bash-3.2
Homebrew 2.1.6
Watchman 4.9.0

expo-cli - Only way I could get it installed was ‘npm install -g expo-cli --unsafe-perm’ ran with sudo permissions. Version: 2.20.2

I can create and run a project, as well as the previous project I’ve been working on by using the standard commands as follows.

cd… (into correct dir)
sudo npm start
(With the Simulator open and manually installed press i)

Then I get the message I mentioned above.

Trying to open the project in iOS simulator…
Downloading the latest version of Expo client app
Installing Expo client on iOS simulator
/

1 Like

I have similar issue…

If I have the simulator open and run

$sudo expo client:install:ios              
Uninstalling Expo client from iOS simulator.
Downloading the latest version of Expo client app
Installing Expo client on iOS simulator
Done!

There is still no Expo app installed on the simulator…

I then did

$sudo chmod -R 777 ~/.expo/

and started it via npm start instead of expo start - it worked…

2 Likes

@e3br did you ever figure out the problem? I am having the same issue.

@adamjnav

I had the same problem, and the cause was that my users/username/.expo as well as my project/.expo folders were owned by root, this was because I installed expo as root. (This already gave some problems earlier where running start expo didn’t work without root privilege)

What solved it for me was to just remove both of those .expo folders and then run start expo again without root privilege this time.

@justinj

3 Likes

chmod 777 is never the right solution for any problem.

I think the problem here was that the ownership was wrong, probably because of running expo init or expo start as root. The fix would be to run something like:

sudo chown -R yourusername:yourgroupname ~/.expo /path/to/your/project
2 Likes

Hello Guys

If you are stuck at this :

And see the expo icon already downloaded on the simulator do that :

https://github.com/expo/expo-cli/issues/933#issuecomment-533840257

For me, an alternative is not typing in the address. Expo app will list projects that are currently running on the local server.

The solution for me was just updating my expo-cli to the latest version

3 Likes

sibertさん、ありがとうございます! You have been real helpful!

Running yarn start instead of expo start worked for me as well.