No internet connection
  1. Home
  2. Support

Trigger Keyboard Maestro Action is broken after MacOS 15.6

By @unnamed_655
    2025-08-21 06:28:27.800Z

    Hello,

    I have been using my streamdeck and soundflow to trigger key Keyboard Maestro macros.

    I recently updated to MacOS 15.6 and it has broken the Trigger Keyboard Maestro Action package.

    I am on Macos 15.6.1
    Soundflow v5.10.8
    Keyboard Maestro Version 11.0.4
    Trigger Keyboard Maestro Action package v1.0.2

    Executing KM macros until now has been flawless, but now there have been many many weird seemingly not obvious bugs that are breaking all of my macros from working properly.

    Simple things like the Copy action in KM are not functioning properly, yet when I trigger these macros natively in KM directly from hotkeys it works fine. Other hard to understand bugs are arising as well.

    More info is in the thread I made on KM forum: https://forum.keyboardmaestro.com/t/upgraded-macos-to-15-6-and-km-has-completely-broken/41930/6

    I suspect that the Trigger Keyboard Maestro Action package is at fault here given its not completely up to date.

    This is the source, it seems somewhat simple if anybody has ideas.

    Solved in post #3, click to view
    • 3 replies
    1. U
      @unnamed_655
        2025-08-21 07:14:39.865Z

        Additionally, I tried executing the KM actions from applescript with automator and it worked okay, so I think that is not the problem

        1. Chad Wahlbrink @Chad2025-08-21 18:17:51.518Z

          Hi, @unnamed_655,

          Two options here.

          You can use the OSAScript Implementation like this:

          const kmName = String(event.props.keyboardMaestroMacroName);
          
          sf.system.execAppleScript({
              implementation: 'OSAScript',
              script: `
                  tell application "Keyboard Maestro Engine"
                      do script "${kmName}"
                  end tell
              `,
          });
          

          By default, sf.system.execAppleScript() now uses NSAppleScript instead. I can get this to work with NSAppleScript as well if I reset the AppleEvents permissions by running this in the Terminal application on Mac:

          tccutil reset AppleEvents
          

          This resets AppleEvents approvals system-wide; you’ll be re-prompted for access from various apps. After approving these prompts, SoundFlow should be able to use either implementation OSAScript or NSAppleScript.

          Let me know if that helps!

          As a quick reminder, to share code on the forum you can follow this tutorial:
          How to quote code in the SoundFlow forum.

          And when asking for help with specific scripts, it's best to use the “Macro and Script Help” Workflow so our team has more information about your system and the script being run.

          Cheers,
          Chad

          ReplySolution
          1. U@unnamed_655
              2025-08-21 21:41:19.934Z

              Hey Chad,

              Your OSAScript implementation worked like a charm. Thanks for this!

              And I'll be sure to use the suggested guidance in the future.

              Cheers