User Tools

Site Tools


assistance:Accessibility_Permission_Problem

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
assistance:Accessibility_Permission_Problem [2018/07/30 21:21]
peternlewis Mojave (Developer Betas 1-4 / Public Betas 1-3)
assistance:Accessibility_Permission_Problem [2018/09/27 21:37]
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. 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 for 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.
  
 (!) 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 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. ​
  
-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.+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.
  
 If you continue to have problems, [[https://​support.keyboardmaestro.com/​|contact support]]. If you continue to have problems, [[https://​support.keyboardmaestro.com/​|contact support]].
  
 ** Historic Mojave Beta information which will be removed when Mojave is released ** ** Historic Mojave Beta information which will be removed when Mojave is released **
 +
 +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 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. 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.
Line 21: Line 23:
 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. 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.
  
-Note that OS X Mojave Beta 4 (Developer Betas 4 / Public Betas 3) will not grant Keyboard Maestro Engine.app accessibility permissions while it is within the Keyboard Maestro.app bundle, so the only way to run the Keyboard Maestro Engine.app with accessibility permissions in beta 4 is to copy the Keyboard Maestro Engine.app out of the bundle and launch it manually. ​ Note that Keyboard Maestro (editor) will relaunch the “correct” version of Keyboard Maestro Engine every time it is launched, so you will have to relaunch the Keyboard Maestro Engine.app each time you launch Keyboard Maestro.app. +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.
assistance/Accessibility_Permission_Problem.txt · Last modified: 2019/07/09 22:06 by peternlewis