-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Can't find simulator for "iPhoneX" #23256
Comments
Can you run If you believe this information is irrelevant to the reported issue, you may write |
We are automatically closing this issue because it does not appear to follow any of the provided issue templates. 👉 Click here if you want to report a reproducible bug or regression in React Native. |
change this file: /node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js line 42, to: if (!version.startsWith('com.apple.CoreSimulator.SimRuntime.iOS') && !version.startsWith('tvOS')) { |
That change works for me, after I have installed latest xcode beta, and removed the beta. |
Facing this after Xcode simulators update to 12.2 (RN 0.57.8). |
For the one who did an update of xCode simulators update. (appeared 27 March 2019) This file: Find line 42, and replace
with something like this:
You still will be able to build your project with xCode. |
I would like to add that it works when building directly from Xcode. |
Environment
I'm running npm inside the react-native app
Just downloaded latest npm and xcode
Description
Reproduce: Running npm run ios, I get that it can't find simulator for "iPhoneX"
Fix / Bugs: in local-cli/runIOS/findMatchingSimulator.js:
L42 which checks that the version of the simulator is an iOS or tvOS always fails (namely, the version of the simulator is com.apple.[some other things].iOs/tvOS. Namely the following if statement checks that the version starts with iOS or tvOS when it should be checking that of the text following the latest period, the text starts with iOs or tvOS.
L55 which was supposed to fix this bug, the isAvailable field is actually boolean true instead of string 'YES'
The text was updated successfully, but these errors were encountered: