Resolving Issues Due to macOS Mojave



Continuing the discussion from Ready for Mojave:

Wiki Post on Resolving Mojave Issues

UPDATED: 2018-11-07 15:41 GMT-6

In addition to the suggestions made by Peter @peternlewis in the above announcement, you might consider the following:

  • You will have to ensure you enable Accessibility for both Keyboard Maestro and Keyboard Maestro Engine. If you have any troubles with accessibility (eg typing keystrokes, selecting menus, copy/paste, etc), you need to toggle the accessibility permissions (System Preferences, Security & Privacy, Privacy, Accessibility) for Keyboard Maestro and Keyboard Maestro Engine off and then on again.


  1. Responding to Mojave: not authorized to send Apple events
  2. Responding to lack of accessibility permissions — @PeternLewis
  3. Accessibility Permission Problem— KM Wiki
  4. Mojave Brings In Big Security Changes — Late Night Software
    • One of the major impacts is the loss of using AppleScript Scripting Additions, like the Satimage.osax that many of us have used for years.
  5. Mojave clipboard behavior and workaround
  6. Mojave date tokens are always English (no good solutions) — @PeternLewis
  7. Mojave unable to simulate system/other application hot keys that use arrows or function keys (no good solutions) — @PeternLewis
  8. Mojave error Using AppleScript to Send JavaScript to Fluid browser -- @deanashton

I have made this topic post a wiki post so that anyone who has additional tips/info about dealing with macOS Mojave can edit/update this post.

Mojave problems
Toggle Do Not Disturb macro not working in Mojave