PSA - Hyperkey breaks for internal keyboard on Beta 26.4

Just a quick heads up that Hyperkey breaks for internal keyboards on the latest beta, external keyboards work fine.
Doesn’t matter how it’s implemented, I’ve seen it reported for raycast, homerow and raycast.

1 Like

What about karabiner elements? That’s the lowest level version of making a hyperkey that I’m aware of

1 Like

yup, that’s what I use. forgot to mention that in my original post. doh.

1 Like

Please report it to Apple.

I use this “key” a lot…

3 Likes

Unfortunately Apple added a new private entitlement ( com.apple.iohid.protectedDeviceAccess) that blocks IOHIDDeviceOpen for Macbook’s built-in keyboards. This seems like an intentional change, but maybe still worth reporting the impact of this change (especially for a dot release) to Apple. This was not private API and it means all apps that relied on this need to use other ways to achieve hyper key functionality. Luckily at least for hyper key this is not too hard to workaround. I have updated the HyperKey in BetterTouchTool to work with 26.4 with the latest alphas.

However this doesn’t paint a nice future for lower level system tools with more and more stuff being locked down.

6 Likes

Thanks, downloading the Alpha now :slight_smile:

I wish Apple would stop this. The Mac should not continue to get more and more locked down. Blocking tool access like this is beyond frustrating. I use the Mac over other platforms because of tools like Karabiner Elements, Keyboard Maestro, BetterTouchTool, etc… If those go away my use of the Mac will go away, and if that happens iOS isn’t far behind. :confused:

2 Likes

Some years ago a lot of Mac users complained about MacOS becoming more and more like iOS and Apple will sooner or later lock everything up and take control of users. I laughed about it, I just saw the beauty and innovations.
Now with Tahoe looking like an iOS game vibecoded by a 13 year old on too much sugar I more and more think the critics were right.

1 Like

Some software will fare better than others. Keyboard Maestro is developed with few if any private APIs presumably in part to hedge against the changing whims of Apple.

This issue isn’t related to private APIs. This was a public API that they’ve now changed to private it seems. :confused:

Apple made the API work again in 26.4 beta 3! :slight_smile:

4 Likes