-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Input Monitoring" permission required #123
Comments
Instead of filing an issue, send a PR with the addition to README.md |
As well as adding it to the README I'll take a look and see if we can explicitly request the permission or check to see if the permissions are valid. I wonder if some of the issue is the change in signing or notarising 🤷 |
Hmm this is weird, there is no entry in the "Input Monitoring" on either of my devices (both M1, both 12.6) and it works perfectly. I wonder if there are certain settings or environments which need this extra permission 🤔 |
PR here: #124 |
I had the same issue, went through same steps of uninstalling and reinstalling as @passaro , and allowing input monitoring fixed this for me - macos 12.5.1, MacBook Pro (16-inch, 2019) |
I had the same issue and allowing input monitoring fixed it for me. I simultaneously upgraded Yubiswitch to the latest version and changed my Yubikey to a FIPS version, so two changes that could potentially be related.
|
@davidrothera Same - I'm on the latest Yubiswitch ( |
YubiSwitch 0.16 was not working on my Mac (M1 Pro, macOS 12.6), even after double checking product&vendor ids, uninstalling, and making sure to set the Accessibility permissions.
I noticed this message in the logs:
With a bit of googling, I found that the error should be
kIOReturnNotPermitted
and got to this post: https://nachtimwald.com/2020/11/08/macos-iohidmanager-permission-issue/Their solution (for a different device/app) also worked for me: allowing “Security & Privacy” -> Privacy -> “Input Monitoring” for YubiSwitch (in addition to "Accessibility" as mentioned in README).
The text was updated successfully, but these errors were encountered: