Hello everyone, I am experiencing a severe, workflow-breaking issue with the new Device Hub implementation in the latest stable release of Xcode 27 running on macOS 27. My development machine is an M1 MacBook Pro with 8GB RAM and a 512GB SSD.The simulator has become completely unusable, forcing a massive degradation in my development workflow. The Problem:100% CPU Consumption: When launching a simulator (iOS 27.0), the system instantly spikes to maximum processor usage. While DeviceHub.app spawns the window, the background processes diskimagesiod and CoreDeviceService relentlessly consume between 50% to 95% CPU each, even when the simulator is completely idle.Total Input Lockout / Broken Shortcuts: Absolutely no keyboard shortcuts pass through to the simulator window (e.g., standard development hooks or navigation). The simulator completely stops responding to touch inputs or hardware button clicks, getting stuck in a rigid runtime loop.Immediate Relief Upon Killing Process: The moment I manually force-terminate devicehub via Activity Monitor or Terminal, my overall system load instantly drops back down to a peaceful 2.48% CPU with ~94% idle.Underlying Error Logs:When launching the binary directly from the terminal via /Applications/Xcode.app/Contents/Applications/DeviceHub.app/Contents/MacOS/DeviceHub --booted, the console outputs a massive stream of critical class duplication conflicts between the native OS and private developer frameworks objc[4489]: Class ..._TTC12UniversalHID26TouchSensitiveButtonFilter is implemented in both /System/Library/PrivateFrameworks/UniversalHID.framework/Versions/A/UniversalHID (0x2ec5a4c8d) and /Library/Developer/PrivateFrameworks/CoreDevice.framework/Versions/A/Frameworks/UniversalHID.framework/Versions/A/UniversalHID (0x105025580). One of the duplicates must be removed or renamed.
objc[4489]: Class ..._TTC12UniversalHID15DigitizerFilter is implemented in both /System/Library/PrivateFrameworks/UniversalHID.framework/Versions/A/UniversalHID and /Library/Developer/PrivateFrameworks/CoreDevice.framework/... One of the duplicates must be removed or renamed.
Impact:Because these private frameworks are deadlocking over registering duplicate input pointers for touch coordinates, scrolling handlers, and button filters, the core virtualization engine hangs.Wiping DerivedData, clearing out iOS DeviceSupport caches, and running xcrun simctl erase all do not resolve the issue. Because the standalone legacy Simulator.app has been entirely removed from /Contents/Developer/Applications/, there is currently no way to bypass this bugged DeviceHub implementation natively.On an 8GB M1 machine, this bug completely thermal-throttles the hardware and paralyzes the local testing pipeline. Is anyone else hitting this linkage deadlock on version 27, or is there a known hidden defaults write flag to decouple input filtering from the CoreDevice workspace loop?
Any assistance or temporary patches from the engineering team would be highly appreciated.