KM and Sonoma

[peternlewis]

@jan.kkm

In Sonoma it only opens the first menu and highlights the "Move to" item without opening it. Then I get a -5620 error in the notification center.

See:

Select or Show a Menu Item action issue with Sonoma

OK, yes, this is basically the same issue. Sonoma for some (all, many, most, a few, I'm not sure) menus returns error -6520 menuNotFoundErr for menus it clearly finds. So selecting Safari File ➤ New Window, works, but then returns menuNotFoundErr. And trying to shoe Safari File ➤ Export fails with the same error. So I would guess Apple has to work to do to resolve this. It's pretty repeatable, and the menu system is all new, so hopefully they will actually resolve it. Otherwise eventually I'll…

[kcwhat]

Hey @cdthomer, I’m guessing you can add me to the team now because I never experienced these issues previously. I’ll maneuver around it as best as I can. Sonoma made a slew of punishing changes. The one that hurt most is that they changed the Voice Control system. Even though this is unrelated, to KM, I used a ton of Voice Control commands with Keyboard Maestro. I went in to add one, this afternoon, and I was unable to see any of my commands. Some error concerning extensions didn’t allow me to. The Voice Commands still worked but I couldn’t add or edit any of them. So I exported the voice command file, in case there was a future solution, and I started from scratch. Thanks for the wild ride Sonoma. I feel bad for those that truly need Voice Control (Accessibility Community). I can’t imagine if they can’t get into their commands to make modifications or add. It’s just a convenience, for me, so I have to take the L. For them, if they have the some issue, it’s going to be bad.

Take care,
KC

[naven87]

I think I found a workaround for my use, although I'm sure there will be a side effect I haven't discovered yet. If I turn off abort on failure for the show menu call, it does open the menu, then I can send keystrokes to navigate.

[drindie]

As others have reported, I'm also getting the -5620 error when trying to open a submenu. The only workaround I could find was to use mouse clicks, which isn't the most reliable when the software makes updates or changes.

I'd recommend NOT updating to Sonoma yet if you have a lot of Macros.

[drindie]

Your work-around worked for me as well. Turning off both the Failure Aborts Macro and Notify on Failure puts a slight pause at that point of the macro, but it works. As you said, could be side effects but for now it's doing what I need.

[cdthomer]

@drindie

I'd recommend NOT updating to Sonoma yet if you have a lot of Macros.

At this point, hearing all the issues Sonoma has created (here and on other forums), I’ll probably just skip it all together.

[kcwhat]

@cdthomer

At this point, hearing all the issues Sonoma has created (here and on other forums), I’ll probably just skip it all together.

Stop being scared and smart!

[Lloydi]

I was getting this oddity before Sonoma. Even something as simple as setting a window to be left 50% could sometimes take several triggers. Never worked out why.

[jorgehhr]

My window management macros are not working properly. For example this macro only resizes the window about 80%, but doesn't fill the entire screen. Same with other 9 macros.

[devoy]

Hmm.. I just read over in the BTT forum a similar report. Andreas says there that Sonoma is mis-reporting the menu height. That may be the problem.

For what it's worth, my own window macros are working fine, but I don't use SCREENVISIBLE.

[jorgehhr]

Hi. It's not just the height is the width too. May I ask what do you use for resizing your windows. Can you share some of them?

[devoy]

D'oh. This is my greatest shame and secret about Keyboard Maestro. I've got this fairly terrific framework for window management and I've never shared it. Many reasons..

1. It's one of my earliest works with KBM..my "journeyman project" so I built it without any thought of sharing it on

2. So it's far from my best work and completely undocumented. I've been meaning to deal with that..

3. Also I "acquired" a bunch of stuff from this forum to make it work, without the necessary attributions (See #1)

4. The stuff I really use works well, but it's not completely tested. (Firing a KBM macro on a window event seemed like a good idea, but it's never really come up in my practice.)

I'm sorry, this sounds like a big tease but it's more of a confession of guilt. I've been meaning to put all this right and share but there's never been time.

But, I'd be more than willing to discuss approaches and features of such a solution with other people, perhaps in another thread.

Oh, your original question: I had to go back to look (it's been a while) Okay, I use the SCREEN() function. But I also keep my menubar hidden most of the time. (+1 to Menuwhere, when you've got a lot of screen real estate you don't want to be dragging your mouse around all day)

That must be why the Sonoma bug doesn't affect me.

I don't know how that helps you, but confession is good for my soul.

[Michiel]

I have exactly the same problem, really weird move/resize behaviour, which for me only started to occur after the 14.1 upgrade and not with the initial 14.0. Never tried the beta. Any ideas on this, @peternlewis ? Thanks!

[peternlewis]

@Michiel

I have exactly the same problem

Exactly what same problem?

I don't know of any window issues in Sonoma 14.1.

[Michiel]

Well, in some applications (e.g. Chrome, Finder... but I have the impression not all the time?) window moving & resizing is not behaving as expected. I have shortcuts to throw windows to the left/right side, to the second monitor, to center, to make full screen etc and they do not do that immediately. E.g. a full screen move first takes like 4/5ths and only on repeating the shortcut it does the full screen. It is really weird.

Thanks & cheers --M.

[cdthomer]

This is a fairly well-documented issue, dating back at least a couple of years.

• Window resize works inconsistently (dependent on App and Mac) - Questions & Suggestions - Keyboard Maestro Discourse
• Possible Bug: Manipulate a Window Interacts Differently (And Unreliably) With Different Applications - Questions & Suggestions - Keyboard Maestro Discourse
• Getting Started with macOS Shortcuts - Questions & Suggestions - Keyboard Maestro Discourse

Note Peter's comments on one particular post:

Getting Started with macOS Shortcuts

Yes, sadly the Accessibility API has a nasty habit of simply ignoring part or all the request to change the window. Apparently there are apps that can make this worse or better by turning on or off an undocumented accessibility parameter. As it is, Keyboard Maestro already executes the Accessibility requests multiple times when making the changes. One thing to try is to simply add a Repeat action around the Manipulate a Window action (and maybe a small Pause as well) and repeat the action 3 t…

[NavyProp]

This workaround helped me. I'm working in Excel trying to select a menu item and this was blowing up. Unticking "Failure Aborts Macro" does allow the action to execute, however it takes noticeably longer and also still triggers the error. I hope KM / Apple comes up with a way to select menu items without this workaround. Thanks for the tip!

[henryone]

My macos upgraded to sonoma and I found the macro to enter my password to unlock safari password manager no longer work.
The macro will look for below screen to show up, then enter the password to unlock it.

It was working flawlessly before the sonoma upgrade. Now whenever this popup screen show up, the macro didn't work, KM shows 'secure input enabled'. In very few cases it worked ok but 90% of case it didn't. Does anyone know how to make it work?

Thanks.

[Mircea.M]

Sonoma is not good in conjunction with KM, I have a lot of slow macros after the upgrade, very laggy. I hope that will be a fix for it.

[henryone]

bad news... my company forced upgrade