New Mac; All Brave Browser actions now using Safari...?

[noisneil]

All the actions that previously interacted with Brave are now using Safari. I'm sure I must have been down this road but I can't think what I've missed.

I've done the usual:

defaults write com.stairways.keyboardmaestro.engine AppleScriptGoogleChromeBundleID -string "com.brave.Browser"
defaults write com.stairways.keyboardmaestro.engine BrowserGoogleChromeName -string "Brave Browser"

Can anyone point me in the right direction?

[kevinb]

You have restarted KM completely?

Are %FrontBrowser...% tokens affected, or only %Chrome…% tokens?

[noisneil]

Yeah, it's a new installation and I've restarted the machine a few times since setting up KM. It's not the tokens but the actions that are the issue. Instead of, for example Set Brave URL, an action will now say Set Safari URL, with the Safari icon instead of Brave's. Not sure how to revert them back to how they were.

[kevinb]

Maybe you could directly edit (in for example BBEdit) ~/Library/Preferences/com.stairways.keyboardmaestro.engine.plist ?

Or just move the file out of Preferences and go from there.

[noisneil]

That sounds a bit nuclear and I'd prefer not to destroy my Safari actions. I'm sure this has happened to someone else, so I'll give it a day or so before I start messing around with the prefs. Thanks for the suggestion though.

Sorry to bother you, but @peternlewis?

[kevinb]

Yes, editing is risky but I think moving the preferences file temporarily should be fine. Alternatively you could set up another account on your Mac to test from. But if you can wait for the authoritative answer that might indeed be best!

[iampariah]

It's some kind of undocumented interaction between Keyboard Maestro and Brave (or something else), or just a bug in KM. It happened to me, too.

Macro to Replace Chrome Actions with Front Browser Actions?

I'm no good at writing macros that affect Keyboard Maestro itself, so before I embark on replacing hundreds of actions by hand, I thought I'd ask: Does anyone have a macro to replace Chrome-centric actions with actions that work with other (not Safari) browsers? Now that Google has come out of the closet as overtly evil, I'm trying to reduce my reliance on Google (Search, Chrome, etc.) and trying out Chromium-based browsers with privacy and security, like Brave, Vivaldi, and so on. I'd like to…

and

I Broke All Safari Actions and Need Help

While trying to solve a related issue I broke all the Safari actions in KM. KM can't control or do anything with Safari any more. Can someone please help me restore them? I'm not sure what command to use in Terminal or somewhere else I might need to change a KM setting. In troubleshooting another issue I issued the following Terminal commands one at a time (with an Enter between) defaults write com.stairways.keyboardmaestro.engine AppleScriptSafariBundleID -string "com.apple.SafariTechnologyPr…

What worked for me was the following:

1. I deleted all the browser preferences in KM per Peter Lewis's post:

defaults delete com.stairways.keyboardmaestro.engine AppleScriptSafariBundleID
defaults delete com.stairways.keyboardmaestro.engine BrowserSafariName
defaults delete com.stairways.keyboardmaestro.engine AppleScriptSafariName
defaults delete com.stairways.keyboardmaestro.engine AppleScriptGoogleChromeBundleID
defaults delete com.stairways.keyboardmaestro.engine BrowserGoogleChromeName
defaults delete com.stairways.keyboardmaestro.engine AppleScriptGoogleChromeName

2. Then I ignored the accepted way to do it.
3. I Created a macro called Primary Browser, set it to Activate Brave Browser.
4. In macros, I first call that Activate Brave Browser macro.
5. Then, the macros send all their commands to the Front Browser or directly to Brave, all manually changed from Default Application or Chrome-specific actions.

I've tried the approved way, replacing Chrome in preferences with Brave, a couple of times; it always ends in either or both KM ignoring the directive and sending to Chrome or Safari, or all browser commands failing.

[noisneil]

Thanks for the really thoughtful response. I ended up going through and adjusting all the affected macros by hand. Didn't actually take that long. If it happens again, I'll refer back to your comment.

[iampariah]

Excellent! I'm glad it wasn't that tough a process for you.