-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Choose Simulator iOS version #10288
Comments
+1 but until then, you can manually build and archive your project via XCode |
@Amurmurmur this looks like a question related to Xcode usage. Please refer to Apple documentation |
this is not an xcode usage problem. xcode can do what i said in #10284. it how the cli uses xcode. |
I found "solution" just delete duplicate simulators with different ios versions I simply removed iPhone 6 10.0 simulator and by default react-native runs iPhone 6 with 9.3 |
how about when i want to run two simulators of the same iphone and ios, but different name, and run something on one, run something else on the other? |
Although I'm a strong advocate of using Xcode, I noticed a combination of issues requesting support for running a specific iOS version with `react-native run-ios`. This is a follow up for changes that were made in the recent past. facebook@48ab5eb facebook@8b55e50 Tested using both `--device` and `--udid ` with various simulator options and devices. Closes facebook#10288
Although I'm a strong advocate of using Xcode, I noticed a combination of issues requesting support for running a specific iOS version with `react-native run-ios`. This is a follow up for changes that were made in the recent past. facebook@48ab5eb facebook@8b55e50 Tested using both `--device` and `--udid ` with various simulator options and devices. Closes facebook#10288
Although I'm a strong advocate of using Xcode, I noticed a combination of issues requesting support for running a specific iOS version with `react-native run-ios`. This is a follow up for changes that were made in the recent past. facebook@48ab5eb facebook@8b55e50 Tested using both `--device` and `--udid ` with various simulator options and devices. Closes facebook#10288
Although I'm a strong advocate of using Xcode, I noticed a combination of issues requesting support for running a specific iOS version with `react-native run-ios`. This is a follow up for changes that were made in the recent past. facebook@48ab5eb facebook@8b55e50 Tested using both `--device` and `--udid ` with various simulator options and devices. Closes facebook#10288
Although I'm a strong advocate of using Xcode, I noticed a combination of issues requesting support for running a specific iOS version with `react-native run-ios`. This is a follow up for changes that were made in the recent past. facebook@48ab5eb facebook@8b55e50 Tested using both `--device` and `--udid ` with various simulator options and devices. Closes facebook#10288
It seems like there is a reasonable workaround here so I am going to close this issue. Thanks folks for chiming in to help answer this! |
@lacker this is a workaround, but not a reasonable one IMO. It requires uninstalling and reinstalling simulators when you want to change the iOS version that |
If I run
Hmm.. looks like 10.2 is still getting called.
|
I have the same question. Is there any way how this can be specified? Are the UUIDs unique? Or are they the same on my local machine and on other machines? Trying to run iPhone 6 with iOS 10.3 |
Vote to reopen. It seems like which iOS version is used is random when multiple ones are installed. It would be really useful to have an option that can configure this! |
@spinningarrow agreed; mine just opened with iPhone 6 9.1 even though the apps deployment target is 9.3... Took me several minutes to debug why the app was dying immediately on opening! I didn't even know I had 9.1 installed... |
+1 to reopen, mine is iPhone 6 8.4 |
+1 |
This is still happening with the iOS 11.1 simulator |
Actually it works for me now if you launch a simulator of your choice (and only one) and then run react-native run-ios, it will use actually launched simulator. |
@comur That's slightly different - that's preloading the simulator and react will use the already open one. The feature request is to be able to specify the version when launching it... Or at least have the launcher know if your project settings define a minimum version, to not use anything less than that. |
I'm also hitting this issue and would like to see it re-opened. Would be great to have three features added in relation to the issue:
|
So I investigated this issue and figured out that the fix for #9414 that added the ability to run on devices broke the original functionality of the
Aside from waiting on a decision for #17284, as that affects the same files and would require a merge for a fix, I don't know if I should be committing any additional time into cleaning up the code logic and writing new tests. Thoughts? Could someone with decision making power chime in here?
Edit: My mistake on the workaround. I was testing on a different code branch where I was working on a udid fix that should address the non-merged closed PR #10405. |
Please reopen |
I executed the command with 'sudo' and it worked.
|
Never ever run with |
This is still an issue, but a decent workaround exists. Launch XCode, select Window > Devices and Simulators, then open the Simulator tab. Rename the simulators you need to whatever you want. You can then use the For example, I renamed my iPhone 6 with versions 9.0 and 11.2 to "Nonary" and "Elevensies" respectively. My command would look like It'd be really good to see an update where you can actually set the iOS version without any workaround, however. |
Completely agree, OS version should be specifiable @lacker |
I think @patrickholley 's workaround is the best thing we can do now |
@lacker please reopen. A clunky workaround doesn't count as a fix. |
Agreed. We have CI that comes with simulators pre-loaded. Renaming and/or uninstalling is definitely not ideal. |
React-native v0.34
Anyway to choose a simulator's ios version to run?
I have list of simulators with iOS 9.3 and iOS 10.
When using --simulator it picks the simulator device with latest iOS which is 10.
Setting deployment target to 9.3 in the project settings doesnt help :/
Maybe a flag --iosversion would be beneficial in the next release.
Thank you very much in advance,
The text was updated successfully, but these errors were encountered: