simctl.extensions.start fails to start new simulator if simulator with different deviceId is already running

[mattjoss]

1. Call simctl.extensions.start(deviceId1)
2. Leave simulator running and call simctl.extensions.start(deviceId2)

Simulator does not switch to deviceId2.

When trying to call simctl.install() after second start, the following error is returned...

An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=159):
Invalid device state

The bug occurs in 0.0.8, but works correctly in 0.0.6

This can be seen with the attached node.js app.
simctl-test.zip

// To test, get list of deviceIds from 'xcrun simctl list' and then run the following command twice with diffeent device ids
//node ./index.js {PATH_TO_APP} {DEVICE_ID}
// e.g.
//node ./index.js ~/HelloWorld.app EAA544F1-D533-4168-9F4A-790AFE764DDA
//node ./index.js ~/HelloWorld.app 3F6912C6-1392-40B7-95CC-41A69EC07BCD

[shazron]

Just checking, is Xcode 7 (Xcode.app) the only Xcode installed in your system?
Probably related to #10

[mattjoss]

Yes, only Xcode 7 installed.

[shazron]

Confirmed. Investigating a fix.

[shazron]

Reverting back to using Instruments fixes this: 704b0f8

[shazron]

The iOS Simulator really doesn't like to have more than one instance "open"ed, which is probably causing the "Invalid Device State". Instruments intelligently shuts down the previous instance and launches the new one.

[shazron]

Fixed in 34426c7