Skip to content
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

Closed
Jeff-Walker opened this issue Apr 25, 2022 · 5 comments
Closed

Comments

@Jeff-Walker
Copy link

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.

@uzak
Copy link

uzak commented Apr 25, 2022

Same problem here.

@dmarcotte
Copy link
Owner

dmarcotte commented Apr 25, 2022

Thanks @Jeff-Walker, @uzak. I was able to reproduce this (not sure if they matter but here are some repro details: I used brew upgrade --cask easy-move-plus-resize and was on new Apple silicon). However, I was also able to fix the issue as follows:

Workaround:

  • In System Preferences -> Security & Privacy, on the Privacy tab under Accessibility, click the Easy Move+Resize entry to select it, then click the minus - button at the bottom of the list
  • Now, relaunch Easy Move+Resize and re-enable it in Accessibility
  • Easy Move+Resize should work now

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.

@uzak
Copy link

uzak commented Apr 26, 2022

Hello @dmarcotte. It worked fine and solved the problem for me. Thank you!

@Jeff-Walker
Copy link
Author

Solved the problem for me too. Thanks for the help.

@dmarcotte
Copy link
Owner

Thank you both!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants