react-native: Similator is not found, Xcode and simulator installed and working properly.
Starting Metro Bundler on port 19004.
Simulator is installed but is identified as ‘com.apple.CoreSimulator.SimulatorTrampoline’; don’t know what that is.
Simulator not installed. Please visit https://developer.apple.com/xcode/download/ to download Xcode and the iOS simulator. If you already have the latest version of Xcode installed, you may have to run the command sudo xcode-select -s /Applications/Xcode.app
.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 42
- Comments: 25 (1 by maintainers)
Links to this issue
Commits related to this issue
- Update README to avoid XCode issue Related issue is https://github.com/facebook/react-native/issues/23878 — committed to k-yokoishi/goobit by k-yokoishi 5 years ago
Running
open -a Simulator
and thennpm start
fixed the issue.Please note this issue tracker is not a help forum (as stated in issue template).
We recommend using StackOverflow where there are community incentives to help others or our Discord channel for questions.
@nahtnam’s solution opens the simulator temporarily, but the next time you open it, you have to run both commands again as well. For now, I am aliasing
start
toopen -a Simulator; expo start
.However, I hope a better solution will be found
@cpojer I think this should be re-opened. We aren’t asking for help, rather we are trying to report a bug.
@cpojer there is a recent StackOverflow issue related. Only 47 views so far, but growing: https://stackoverflow.com/questions/55202064/expo-react-native-ios-simulator-not-working I’ll post any solution/workaround I find in there. This looks like a proper bug.
I noticed XCode was updated recently. Could it be related to this? I am having this problem, with expo, using version 10.2 of XCode (SimulatorApp-880.5 CoreSimulator-587.35)
Anyone having this with a different version of XCode?
I’ve noticed that Simulator is not gracefully exiting after closing. This is true whether or not I even run expo while it is open.
If I kill all the tasks named “Simulator” (which for some reason, cant use killall even thought they ar running as my user, have to
kill -9
those PIDs), then expo returns to working normally … until I close the Simulator again. Because I have to use -9 , _something _ is zombieing.Same issue, running
sudo xcode-select -s /Applications/Xcode.app
does nothing, @nahtnam solution with opening simulator first from CLI is also not working, it gives meOperation timed out
.Just a followup, I’ve since upgraded to the 10.14.4 release, of course rebooted, and continued my development - I now can use
killall
. I have to do this with some frequency: nearly every time I introduce a coding error that halts recompile (like unmatched parenthesis, etc), pressing ‘r’ in the console running expo does not reiniitialize the build. The Simulator gets stuck with a red screen that won’t dismiss. if instead I relaunch the. app in ios, it goes to a blue screen but no rebuild occurs.I am finding the best route to continue is to have two terminal tabs open, with these commands on tap:
expo r -c
killall Simulator && open -a Simulator