-
Notifications
You must be signed in to change notification settings - Fork 77
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
Asks for Accessibility but already has it after update to 1.5.0 #79
Comments
Same problem here. |
Thanks @Jeff-Walker, @uzak. I was able to reproduce this (not sure if they matter but here are some repro details: I used Workaround:
The root cause here seems to be Accessibility whitelist becoming "stale" on new builds, not allowing the old Easy Move+Resize permission entry to apply to the new binary. This makes a lot of sense from a security perspective, but the user experience around it is not helpful at all. The steps above work around this, "refreshing" the permission for the new build. Please let me know if that sorts y'all out, and thanks again for reporting. |
Hello @dmarcotte. It worked fine and solved the problem for me. Thank you! |
Solved the problem for me too. Thanks for the help. |
Thank you both! |
This works, with a minor drawback. When I remove the app from Accessibility settings, both the keyboard and mouse stop working. The mouse pointer moves, but I can't type or click. I have to power-cycle the Mac to regain control. Re-adding the app afterward resolves the issue. |
I've been using the app for a while now, but I guess I updated it via brew and now it when it starts, it requests accessibility permissions. When I look at the settings, it already has it.
I've tried unchecking and checking it, reinstalling with brew and uninstalling it, then installing it. Same thing. If I choose "deny", the app doesn't start.
The text was updated successfully, but these errors were encountered: