Xcode 27 Device Hub unable to create simulator

Question

Created 1w

Replies 6

Boosts 5

Participants 6

I am testing the Xcode 27 Beta and new Device Hub app on my MacBook Pro (M5) with macOS Tahoe 26.5.1, but every time I try to create a new Simulator, the process begins to run, but then fails after this message appears that says “Family quit unexpectedly." I looked over the details of the issue, and it is indeed directly linked to the failing simulator creation. Since this issue makes it impossible to Build and Run any app in the new Xcode 27 beta, it makes it almost completely useless for me. I have already downloaded the iOS 27 simulator, but it fails to boot in the Device Hub.

Answered by Developer Tools Engineer in 894123022

This is due to a known issue in Beta 1 where CoreDevice is not using the newly installed CoreSimulator content, leading to no simulators showing up. The best workaround is to run kill -9 CoreDeviceService in Terminal to get CoreDeviceService to restart and pick up the new simulator content (you shouldn't need to reboot your Mac).

Answer 1

l00 OP

1w

I have the same issue.

Answer 2

reed.1325 OP

1w

Same issue here. The fix is to either fully reboot your machine or run killall -9 CoreDeviceService in Terminal.

Let's keep this thread active for all that experience this, since we shouldn't need a fresh reboot to install Xcode!

Answer 3

l00 OP

1w

Accepted Answer

Confirmed, works after reboot.

Answer 4

JKStudios OP

1w

Thank you, @reed.1325 and @l00! I rebooted my device, and Device Hub is now working. I realized, by the way, that the simulators I created in Device Hub were being created in the Simulator app. Hopefully this gets fixed in the next beta

Answer 5

B347 OP

6d

Oh!

I realized, by the way, that the simulators I created in Device Hub were being created in the Simulator app. Hopefully this gets fixed in the next beta

Answer 6

Developer Tools Engineer OP

Apple

13h

Recommended

This is due to a known issue in Beta 1 where CoreDevice is not using the newly installed CoreSimulator content, leading to no simulators showing up. The best workaround is to run kill -9 CoreDeviceService in Terminal to get CoreDeviceService to restart and pick up the new simulator content (you shouldn't need to reboot your Mac).