Doesn't work at all on Catalina 10.15.6 (Workaround Available, need Input Monitoring permission)
Ryanauger95 opened this issue · comments
Describe the bug
Doesn't work at all on Catalina
To Reproduce
Steps to reproduce the behavior:
- Set any/all key delays to 999ms, theen taap a keey twice. I'm not deleting those eduplicates, becausee it shows that unshaky is not working.
Expected behavior
This shouldn't be happening at all. The keys shouldnt be duplicated.
Desktop (please complete the following information):
- macOS version: 10.15.6
confirming the issue on 10.15.6 with error in Console.app:
{ID: com.nestederror.Unshaky, PID[62421], auid: 503, euid: 503, binary path: '/Applications/Unshaky.app/Contents/MacOS/Unshaky'} attempted to call TCCAccessRequest without the com.apple.private.tcc.manager.check-by-audit-token entitlement
I don't know if it is due to I just renewed my Apple developer program membership. I will upload a new build to see if it can fix it
I am still getting the error. Don't have a solution yet
Hello. I had the same error on Catalina and Big Sur, and recently I've got Unshaky app (v.0.6.0) work on macOS Big Sur (beta, 20A5384c).
- Close Unshaky app
- System Preferences -> Security & Privacy -> Privacy -> Accessibility -> delete Unshaky app -> add Unshaky app
- System Preferences -> Security & Privacy -> Privacy -> Input Monitoring -> delete Unshaky app -> add Unshaky app
- System Preferences -> Security & Privacy -> Privacy -> Developer Tools -> add Unshaky app
- Relaunch Unshaky app
Hope this helps.
System Info
- Hardware: MacBook Pro 13-inch (Late 2016)
- OS: macOS Big Sur Public beta
- Unshaky version: v0.6.0
$ spctl --status
assessments disabled
I use macOS with Gatekeeper partially disabled.. (related?)
Thanks, @azk-mochi! I didn’t need to do step 4 (Developer Tools). I also found that enabling the “ignore external keyboard” option stopped the app from working.
Thank you @azk-mochi for the workaround.
I tested it on my macbook and it works. My spctl --status is enabled and I did not add Unshaky to "Developer Tools."
I am unable to reproduce this bug on 10.15.7 (19H15) using Unshaky 0.6.0.
The workaround does not work for me with 0.7.0 on macOS 10.15.7 (19H114) :(
The workaround does not work for me with 0.7.0 on macOS 10.15.7 (19H114) :(
Had the same problem with 10.15.7 (19H114) and Unshaky 0.7.0, even though all permissions had been set in the preferences.
After some time it started working for me for whatever reason (maybe a reboot solved it?).
The workaround does not work for me with 0.7.0 on macOS 10.15.7 (19H114) :(
Did you make sure that the box was checked in Accessibility? I didn't have it checked by default and when I did check it, version 0.7.0 of Unshaky worked on my macOS Catalina 10.15.7.
Close this issue, the workaround is good enough.
I'm unable to add it to "input monitoring" on macOS Catalina 10.15.7. This renders the app unusable. Does anyone have any suggestions?
I'm unable to add it to "input monitoring" on macOS Catalina 10.15.7. This renders the app unusable. Does anyone have any suggestions?
Did you check out #172? (specifically this comment)