Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Similator is not found, Xcode and simulator installed and working properly. #23878

Open
unutoiul opened this issue Mar 13, 2019 · 18 comments

Comments

Projects
None yet
@unutoiul
Copy link

commented Mar 13, 2019

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.

@react-native-bot

This comment has been minimized.

Copy link
Collaborator

commented Mar 13, 2019

Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety?

👉 Click here if you want to take another look at the Bug Report issue template.

@fozzarelo

This comment has been minimized.

Copy link

commented Mar 26, 2019

Same issue.

@nahtnam

This comment has been minimized.

Copy link

commented Mar 26, 2019

Same here, ran the given command as well

@nahtnam

This comment has been minimized.

Copy link

commented Mar 26, 2019

Running open -a Simulator and then npm start fixed the issue.

@kubapyla

This comment has been minimized.

Copy link

commented Mar 26, 2019

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 me Operation timed out.

@cpojer

This comment has been minimized.

Copy link
Contributor

commented Mar 26, 2019

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.

@cpojer cpojer closed this Mar 26, 2019

@fozzarelo

This comment has been minimized.

Copy link

commented Mar 26, 2019

@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.

@cmackenz

This comment has been minimized.

Copy link

commented Mar 26, 2019

I'm having the same issue after upgrading expo-cli to 2.13.0.
Downgrading to 2.11.9 did not resolve the issue.

@fozzarelo

This comment has been minimized.

Copy link

commented Mar 26, 2019

@nahtnam

This comment has been minimized.

Copy link

commented Mar 26, 2019

@cpojer I think this should be re-opened. We aren't asking for help, rather we are trying to report a bug.

@cpojer cpojer reopened this Mar 26, 2019

@prigoose

This comment has been minimized.

Copy link

commented Mar 26, 2019

@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 to open -a Simulator; expo start.

However, I hope a better solution will be found

@GuillaumeRZ

This comment has been minimized.

Copy link

commented Mar 27, 2019

Hey ! Got the same issue right here...

@robbiemu

This comment has been minimized.

Copy link

commented Mar 29, 2019

Rather than simply looking at this as a bug to be fixed, the community desperately needs better documentation of how this is designed to work. -- and by "this" I don't mean what apple has to say about xcode simulator, I mean what react-native scripts are doing, and what configurations must be in place for it to work.

@fozzarelo

This comment has been minimized.

Copy link

commented Mar 29, 2019

Trying to narrow it down...
I think It’s a bug. 🐜
Is this related to expo?
Everyone afected using expo?

@robbiemu

This comment has been minimized.

Copy link

commented Mar 29, 2019

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 -9those PIDs), then expo returns to working normally .. until I close the Simulator again. Because I have to use -9 , _something _ is zombieing.

@robrecord

This comment has been minimized.

Copy link

commented Apr 1, 2019

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?

@robbiemu

This comment has been minimized.

Copy link

commented Apr 1, 2019

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
@robrecord

This comment has been minimized.

Copy link

commented Apr 1, 2019

I also experience an issue when using older versions of react-native, as used in Ignite and expo. It may be related to this issue.

The following was happening using an old react-native version (0.57.8) installed with Ignite.
My version of Expo uses react-native 0.57.1 and also has an issue.

Initializing a react-native project using the latest version 0.59.3 doesn't have this issue.

$ react-native run-ios

Found Xcode project myAwesomeProject.xcodeproj

Could not find iPhone X simulator

Error: Could not find iPhone X simulator
    at resolve (/Users/username/Apps/myAwesomeProject/node_modules/react-native/local-cli/runIOS/runIOS.js:149:13)
    at new Promise (<anonymous>)
    at runOnSimulator (/Users/username/Apps/myAwesomeProject/node_modules/react-native/local-cli/runIOS/runIOS.js:134:10)
    at Object.runIOS [as func] (/Users/username/Apps/myAwesomeProject/node_modules/react-native/local-cli/runIOS/runIOS.js:106:12)
    at Promise.resolve.then (/Users/username/Apps/myAwesomeProject/node_modules/react-native/local-cli/cliEntry.js:117:22)

Also reported here back in February: https://stackoverflow.com/questions/54504076/react-native-run-ios-returns-error-could-not-find-iphone-x-simulator which has a few details about why this is happening. From what I can gather, it had to do with a version number being reported in a way that react-native doesn't correctly parse. Looking at the code they reference, it's since been updated in react-native.

k-yokoishi added a commit to k-yokoishi/goobit that referenced this issue Apr 8, 2019

@react-native-bot react-native-bot added the Bug label May 3, 2019

@hramos hramos removed the Type: Bug Report label May 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.