Closed tlv closed 8 years ago
Any word on what works? I'm stuck on this too.
I too am experiencing this issue and would appreciate any input. After launching the incorrect simulator, the tests never get ran with error "iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1." So it seems it boots the incorrect simulator and then fails when expecting the correct simulator. I tried snapshot reset_simulators and cleaning to no avail.
This issue was migrated to https://github.com/fastlane/fastlane/issues/1664. Please post all further comments there.
fastlane
is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo :rocket:
Hi,
Snapshot sometimes launches the wrong simulator when I run it. What seems to happen is it will just launch the last simulator that I launched from Xcode (e.g. after running my UI tests in Xcode to verify that they were working), regardless of which simulator it is supposed to be launching. For example, snapshot will say it is running the UI tests on the iPhone 6 simulator, and then proceed to launch the iPhone 4s simulator.
This behavior is then followed by the launched simulator failing to boot (it just black screens for 2 minutes), and I get the following error:
iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.
Running
snapshot reset_simulators
had no effect on this problem, although it did cause a different simulator (but still the wrong one) to boot.Has anyone else had this issue before?
Stacktrace:
Snapfile: