Differences

This shows you the differences between two versions of the page.

--- assistance:Accessibility_Permission_Problem [2018/09/26 00:33]
peternlewis
+++ assistance:Accessibility_Permission_Problem [2022/12/02 03:09] (current)
peternlewis
@@ Line 7: / Line 7: @@
 On modern macOS, you enable Accessibility permissions by opening System Preferences, going to the Security & Privacy preferences, and in the Privacy pane select Accessibility and ensure that both Keyboard Maestro and Keyboard Maestro Engine are ticked.
-(!) Note that for Mojave (Developer Beta 5 / Public Beta 4) you may need to relaunch the Keyboard Maestro Engine or make any change to your macros after enabling accessibility.
+(!) Note that in Big Sur and later, as well as the issues described here, you will need to ensure that either Keyboard Maestro is not listed, or has Input Monitoring permission - Input Monitoring permissions can override accessibility permissions.
-(!) Note that OS X Yosemite (10.10 GM1 through 10.10.2) has a serious problem adding applications to the accessibility pane properly. This bug was largely resolved in Yosemite 10.10.3. So if you are having problems with accessibility under Yosemite, upgrade to 10.10.3 or later, and then launch Keyboard Maestro.
+(!) Note that for Catalina continues the tradition started in Mojave of being difficult with the Accessibility permissions, and I have several reports of people having troubles enabling accessibility for Keyboard Maestro Engine.  You should report this to Apple using the Feedback mechanism.  Remove the Keyboard Maestro Engine entry from the accessibility permissions, then quit and relaunch the Keyboard Maestro Engine (in Keyboard Maestro, File ➤ Quit Engine, File ➤ Launch Engine) to re-add it, and then you should be able to enable it.
-If you continue to have problems with enabling Accessibility permissions, ensure you only have one copy of Keyboard Maestro on your Mac and restart and try again.
+(!) Note that since Mojave it is fairly common for the accessibility checkboxes to be on but Keyboard Maestro still not have permission.  Generally toggling the accessibility permissions checkboxes off and on resolves the issue.  Alternatively, deleting the entries and letting the system re-create them usually works if toggling is not sufficient.
-If you continue to have problems, [[https://support.keyboardmaestro.com/|contact support]].
+If Keyboard Maestro or Keyboard Maestro Engine are not listed in the Accessibility list, try restarting each of them. In Keyboard Maestro, choose File ➤ Quit Engine, File ➤ Launch Engine to restart the Keyboard Maestro Engine. Then quit and relaunch Keyboard Maestro. If that does not work, try Restarting and repeat the process. Failing that, you can drag the Keyboard Maestro.app in to the list, or control-click on the Keyboard Maestro.app, and select Show Package Contents, Contents, MacOS and then drag the Keyboard Maestro Engine.app in to the list.
-** Historic Mojave Beta information which will be removed when Mojave is released **
+If you continue to have problems with enabling Accessibility permissions, ensure you only have one copy of Keyboard Maestro on your Mac, that it is in the /Applications folder, that you moved it there **using the Finder** and restart and try again.
-Note that OS X Mojave (Developer Betas 1-4 / Public Betas 1-3) has a serious problem adding accessibly for Keyboard Maestro Engine.  Specifically after it is added, you can click the checkbox but it wont necessarily turn on.  Resolve this by deleting the Keyboard Maestro Engine entry from the Accessibility list and relaunching Keyboard Maestro Engine (Keyboard Maestro File ➤ Quit Engine, File ➤ Launch Engine), and then you can check the checkbox to enable accessibility permissions.
+If you continue to have problems, you can use the `tccutil reset Accessibility` command to reset the Accessibility permissions.
-Note that OS X Mojave (Developer Betas 1-4 / Public Betas 1-3) has a further serious issue in that even after it claims to have enabled accessibility permissions, the system may still be refusing to allow access to the event queue (symptoms include not being able to set hot keys and typed keystrokes not working (including Command-V for paste)).  Restarting your Mac seems to resolve this.
+If you continue to have problems, [[https://support.keyboardmaestro.com/|contact support]].
-Note that OS X Mojave Beta 4 (Developer Betas 4-6 / Public Betas 3-5) will not grant Keyboard Maestro Engine.app accessibility permissions while it is within the Keyboard Maestro.app bundle at all.

Keyboard Maestro Wiki

User Tools

Site Tools

Differences

Page Tools