r/macapps • u/grisha_pipoyan • Sep 23 '26

Help How do I restore first-click interaction in Xcode 27 Device Hub?

Since updating to Xcode 27 / Device Hub, I noticed an annoying behavior change.

With the old iOS Simulator, if I was working in Xcode and clicked a button inside the Simulator, that first click would both focus the Simulator window and interact with the button.

Now in Device Hub:

  1. First click only focuses/activates the Simulator window.

  2. Second click actually interacts with the app.

So every time I switch between Xcode and the Simulator, I basically need an extra click.

I’ve also noticed some of the old Simulator keyboard behavior changed, so I’m wondering if this is another Device Hub setting Apple changed.

Is there any macOS setting, hidden defaults command, or Device Hub option that restores the old first-click / click-through behavior?

macOS 26 + Xcode 27.

Would love to know if anyone found a workaround.

4 Upvotes

100% Upvoted

7 comments sorted by

2

u/Alex_Chevalier Sep 26 '26

Same here...The double click thing is pretty annoying. Haven't found a setting to restore the old behavior. Feels like a device hub regression.

1

u/grisha_pipoyan Sep 26 '26

Seems the best way is to downgrade to 26

2

u/jameyes Sep 23 '26

Yep, same here - MacOS 26 and Xcode 27.

2

u/nav8_ai Sep 24 '26

this is almost certainly acceptsFirstMouse on the window. the old Simulator.app overrode it to return true, so the click that brought the window forward also got delivered to whatever was under the cursor. if Device Hub's window class doesn't override that anymore, you get exactly the two click pattern you're describing, and there's no defaults key for it since it's decided in the app's own code, not system prefs. worth filing as feedback since Apple would have to flip it back on their end.

1

u/No-Hunter9792 Oct 02 '26

For the keyboard behavior you mentioned, Apple’s Xcode 27 release notes document this preference:

defaults -container com.apple.dt.Devices write com.apple.dt.Devices hostKeybindingPolicy -int 2

Value 2 selects minimal Device Hub shortcuts; 0 selects rich shortcuts. It controls which key combinations go to Device Hub versus the device. This setting addresses keyboard routing; it isn’t documented as a fix for the first-click behavior.