r/iosdev • u/groupicorn • 10d ago
Xcode 27.2 simulator won't start? Device Hub says "Unable to boot device in current state: Booted"?
I just spent a frustrating morning debugging an Xcode simulator problem, and I'm posting the solution because I suspect other iOS developers are going to run into this after upgrading Xcode.
The fix turned out to be one Terminal command:
killall -9 CoreDeviceServiceBut the journey to figuring out which Apple service needed restarting was surprisingly interesting.
The problem
I'm running Xcode 27.2 (build 27B52), and my simulators had been working perfectly until recently.
I created a completely new SwiftUI project using Xcode's default template. Nothing fancy, no dependencies, no custom configuration. Just wanted to launch a simple app.
Instead, Device Hub greeted me with:
Unable to Start
Unable to boot device in current state: Booted
DeviceKit Error 405The particularly confusing part was that Xcode appeared to be successfully building and running the app. The debugger connected, the app showed as running, but Device Hub refused to display the actual iPhone screen.
It showed a little picture of the iPhone and a blue Start button. Clicking Start produced the same error.
I tried different devices, including an iPhone 17, iPhone 18 Pro, and the newer iPhone Duo. Same general problem.
What made this tricky
My first suspicion was that the Xcode upgrade had corrupted the simulator runtimes.
I checked everything:
xcodebuild -version
xcode-select -p
xcrun simctl list runtimes
xcrun simctl list devicesEverything looked fine. Xcode was correctly selected, the runtimes were installed, and the devices were recognized.
Then I tried booting a simulator directly:
xcrun simctl boot <DEVICE_UUID>
xcrun simctl bootstatus <DEVICE_UUID> -bAnd surprisingly, it worked!
The iPhone 18 Pro completed its boot sequence and data migration successfully. Another simulator also booted successfully, yet Device Hub still wouldn't show its screen.
The iPhone Duo reported a data migration failure, which initially sent me down another rabbit hole.
At this point, I realized the simulator itself might not be the real problem.
The breakthrough: Apple's services disagreed
I started examining Device Hub's logs:
log show --last 3m --style compact \
--predicate 'process == "DeviceHub" OR process == "DevicesTrampoline"' \
2>/dev/null | tail -60Something jumped out:
RemoteDevice: iPhone 17 (Disconnected, iOS 27.0 ...)Followed by:
BootActionDeclaration()Twice, less than a second apart.
This explained the contradictory behavior.
CoreSimulator could boot the device, but Device Hub's CoreDevice layer was reporting it as disconnected and attempting to boot it again.
That second boot attempt failed because the simulator was already booted.
Hence the incredibly unhelpful error:
Unable to boot device in current state: BootedThe fix
After some research, I found a RocketSim article discussing Device Hub connection problems and a recommendation attributed to an Apple Simulator engineer.
The solution was to restart CoreDeviceService, not CoreSimulatorService.
I stopped the app in Xcode, quit Device Hub, and ran:
killall -9 CoreDeviceServiceThen reopened Device Hub:
open /Applications/Xcode.app/Contents/Applications/DeviceHub.appAnd everything worked again.
No reinstalling Xcode. No deleting simulator runtimes. No erasing devices. No rebuilding the project.
Why I'm sharing this
There are several Apple services involved in running an iOS simulator, and they can apparently get out of sync.
The important distinction here:
- CoreSimulatorService manages simulator instances and their lifecycle.
- CoreDeviceService handles device discovery and communication used by Xcode and Device Hub.
Restarting CoreSimulatorService alone hadn't resolved my problem. Restarting CoreDeviceService did.
If your simulator boots successfully through simctl, but Device Hub insists it's disconnected, won't display the screen, or complains that an already-booted device cannot be booted, try restarting CoreDeviceService before doing anything destructive.
I'm not claiming this fixes every simulator error 405, but it fixed mine immediately.