-
Notifications
You must be signed in to change notification settings - Fork 890
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
"iPhone X" simulator is disabled #739
Comments
F*ck apple: Workaround solution awaiting fix (is was no able to find where is the default in the cli source code…) :
|
The message I got from @bartolkaruza having this issue:
Have you tried restarting Xcode and Simulator as well? |
@satya164 this seems like a bug in Simulator, likely because Catalina is still in beta |
@thymikee XCode 11 is stable though |
Another workaround is to add back the removed iPhone X in Simulator's Hardware > Device > Manage Devices menu |
I met the same problem and @wbadam 's workaround works fine to me. 👍 |
I change my package.json to solve this temporarily: "scripts": { |
Great, it solved the problem |
Where is the default set for "iPhone X" in the source code? anyone knows? |
I have downloaded ios 10 and it automatically added iPhone x and other devices |
iPhone 8 seems to be present in all the simulator runtimes from iOS 11.4 to 13.1, so it seems like the best possible default for now:
|
This have been fixed by #758 |
@codler thanks for linking this. It's fixed for RN 0.61. We'll soon release patch versions for older versions, please be patient. |
@thymikee is there a solution for older versions? |
never mind, I found the solution. inside: .../node_modules/@react-native-community/cli/build/commands/runIOS |
This comment has been minimized.
This comment has been minimized.
@lchenfox you can also update the |
Okay. Thanks a lot. I'll have a try @thymikee |
React Native version: 0.60.4
Steps to reproduce
The Xcode is updated version 11 and the "iPhone X" simulator is disabled and cannot be run with an existing "react-native run-ios".
The text was updated successfully, but these errors were encountered: