-
Notifications
You must be signed in to change notification settings - Fork 883
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
run-ios does not run on simulator by default, presumably because it's trying to run on my iPhone #2254
Comments
Hey @swrobel, we'll change sorting device, so first it would try running on simulator not on physical device. But |
Just to be clear both |
@szymonrybczak I finally had the opportunity to test this now that React Native 0.74 is released with the new cli, but the behavior does not seem to be improved. In this case, I'm attempting to run my app with the "iPhone 15 Pro Max" simulator already booted. My personal iPhone 15 is connected via wifi, which is why you can see it referenced below:
|
Ah, okay so we're launching app in opposite order to the way we log them - fixed in #2364, log were not aligned with actual implementation. Also I've shipped a small fix, so if you few simulators launched and you have your preferred one - it'll preferred one even if not inside
In my personal experience launching on physical devices fails often than launching app on simulator, so we prioritize simulators over devices. Still in your scenario command will fail, but at least app will launch on simulators. I don't know we can improve expierence here 🤔 Fixes will ship in next patch for 0.74. Sorry for trouble and thanks for testing! 🙏 |
Environment
Description
When running
yarn ios
, I expect it to run on the current open & running simulator, or to boot and run on an appropriate simulator. In the example shown below, I have the "iPhone SE (3rd generation)" already running, but the result is the same if it isn't running. It seems to try to useios-deploy
to install it onto my iPhone (connected to my computer via wifi only), rather than installing on the simulator.I have also tried previously running with
--list-devices
and choosing the iPhone SE so that it is "sticky," but that doesn't seem to have any impactBoth of these places state that
run-ios
should open on a Simulator:Reproducible Demo
I can put together a repro if necessary, but I believe this behavior is tied to the CLI, and not to anything specific to my app's code. As is the case with the default template generated, my
package.json
under the"scripts"
section defines theios
command as such"ios": "react-native run-ios"
The text was updated successfully, but these errors were encountered: