-
Notifications
You must be signed in to change notification settings - Fork 18
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
Accessibility Error is in error #18
Comments
I've the same problem.... |
same :( |
*** found this online now it works Seems to be working fine with a small workaround. If you try to open it like normal it will ask you to enable certain permissions, even if you’ve already enabled them. Instead of opening LES like normal, right click it and choose ‘show package contents’. Then open the item called ‘hammerspoon’. This will allow it to work for some reason. Make a shortcut for ‘hammerspoon’ on your desktop and open this anytime you need to open Live Enhancement Suite. |
This didn't worked out for me, still the same windows pops up that Accessibility ist not enabled but it is. Can you share a screenshot of the "hammer spoon" folder? |
you have to autorize terminal too in accessibility |
still haven't been able to get around this |
Same issue here :( |
I managed to open Hammerspoon using:
(and then typing my password) |
Same issue with privacy settings :( |
Duplicate of #6 |
Describe the bug
Upon trying to Open LES I receive an error that LES is not enabled in preferences, but it is.
Screenshots
Please see attached files.
Desktop (please complete the following information):
Additional context



Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: