Date
1 - 2 of 2
Running on multiple simulators from Xcode
Alex Zavatone
Hi. I was of the assumption that we used to be about (Xcode 10?) to be able to run multiple iOS Simulators from one project. In Xcode 13.1, it appears that if I select another iOS Simulator and click run, it stops running the currently running app.
I remember this because I remember needing to select the executable that I wanted to stop within previous Xcode versions.
Did we used to be able to do this? Is there some defaults parameter that has to be set to do this? Or am I just remembering incorrectly?
Thanks in advance,
Alex Zavatone
I remember this because I remember needing to select the executable that I wanted to stop within previous Xcode versions.
Did we used to be able to do this? Is there some defaults parameter that has to be set to do this? Or am I just remembering incorrectly?
Thanks in advance,
Alex Zavatone
On 17 Jun 2022, at 9:20 am, Alex Zavatone via groups.io <zav@...> wrote:In the past I've certainly run apps in concurrent simulator sessions, although I can't remember whether it used to preempt the current one on "Run" or not.
Hi. I was of the assumption that we used to be about (Xcode 10?) to be able to run multiple iOS Simulators from one project. In Xcode 13.1, it appears that if I select another iOS Simulator and click run, it stops running the currently running app.
In any case, you can work around this by launching the second instance manually in the Simulator, and then attach to it once it's up (Debug > Attach to Process > Likely Targets).
There *does* appear a bug in Xcode 13.4.1 where the process selector pop-up thingy (above the console area) mislabels the simulator names, at least in my test just now. Both processes are named the same, as though they belong to the simulator instance, when in fact that's not the case. But notwithstanding that, they allow you to switch between the focused processes as you'd expect.
-ben