Specific hotkey trigger issue for Workflows

[Bill934628]

I have been using a list of workflows triggered by hotkey combo. For example, pressing key combo
OPTION + 1 opens Google Chrome

OPTION + 2 opens Terminal

OPTION + 3 opens Firefox

etc

 

In Alfred, each workflow is set up with a "Hotkey" connected to a "Launch Apps/Files"

This had been working great for about 10 different applications, until an upgrade to Sequoia seems to have broken the functionality in a specific way. It does not work ONLY when I am using the Terminal and use a Hotkey shortcut to switch to a different app. Instead of switching to the different app, I seem to get alternate keyboard chars entered in the terminal such as £¢∞§.  

 

Fixes I've tried:

- Upgrade Alfred. (did not fix the issue)

- Change the Hotkey combo to use a different modifier key. WORKS: eg OPTION + CTRL + 1. But I rather not have to do this...

 

Note: OPTION + SPACE still works as expected: invokes the Alfred omni-search.

 

Thanks!

Edited December 5, 2024 by Bill934628
Fix typo.

[vitor]

15 hours ago, Bill934628 said:

until an upgrade to Sequoia seems to have broken the functionality in a specific way.

 

Yep, that is exactly what happened. It is breaking behaviour purposefully introduced by Apple. I recommend you use the Feedback Assistant app on your Mac to let them know you disapprove.

 

That said, I am not able to reproduce the issue. But @drgrib is, and found that it affects other apps on their machine too (specifically Rectangle Pro). Maybe together you can figure out what your systems have in common and discover why you specifically are affected.

 

 

[zeitlings]

20 hours ago, vitor said:

Yep, that is exactly what happened. It is breaking behaviour purposefully introduced by Apple. I recommend you use the Feedback Assistant app on your Mac to let them know you disapprove.

 

FYI, from the thread you linked:

 

Quote

This issue has been addressed in macOS 15.2 Beta 2 (Build: 24C5073e). The hotkey API now allows hotkeys with only Option (or Option-Shift), without also requiring Command or Control modifiers.

 

With a little luck, this change will soon be reverted.

[vitor]

Nice find, thank you for pointing that out. There is a comment on that reply of someone saying they updated to the beta and it wasn’t fixed, but at least it shows intent.

[Bill934628]

I just had a chance to test out this setup/bug on a new laptop with Sequoia and I could NOT replicate it. I guess that is good news :).

My next steps with debugging the original issue would be to reinstall Alfred.

[Bill934628]

It turns out that there is a menu option in the macOS Terminal (Terminal -> Secure Keyboard Entry) that can be toggled. This corrected the OP issue. I suppose the Sequoia upgrade toggled it on... or another upgrade that tagged along with it.

[Ran]

On 12/19/2024 at 2:32 PM, Bill934628 said:

It turns out that there is a menu option in the macOS Terminal (Terminal -> Secure Keyboard Entry) that can be toggled. This corrected the OP issue. I suppose the Sequoia upgrade toggled it on... or another upgrade that tagged along with it.

 

THANK YOU. This is what solved it for me. Another app had turned on secure keyboard entry (1Password) and restarting that one has toggled it off, allowing Alfred's hotkey to work again.