superficial

I have this exact issue too. I have the same phenomenon in both Safari and Brave browsers (haven't tried others). It appears (to my uninformed self) that Mac OS is probably blocking Alfred when in a password field, but there's then a second phenomenon whereby even after shifting focus / tabs, the hotkey (Cmd+space) doesn't activate Alfred. However, if I 'toggle Alfred' from the menu bar TWICE (presumably once to turn the invisible instance off, and then once to turn it back on again), it reappears, and my hotkey works again. In fact, if I toggle it off using the menu bar, I can summon Alfred with Cmd+Space, as usual. Interesting re: Apple Watch. I'm using an Apple Watch to unlock, although I tried locking the Mac and unlocking with TouchID and the same things happened. Perhaps if restarted and logged back in again without using my watch it might be different, but the fix you mention doesn't seem to help. Also the same with/without BetterTouchTool running. To be honest it's not a major issue for me. It's just a weird bug. I get the Console message above, and also this one: Since sending application [sess=100005 pid=903 uid:501,501,501 g:20,20 pV:2298] is not permitted to send this AppleEvent to this process, returning an errAEEventNotPermitted reply. Alfred 4.6.1 [1274], no powerpack MacOS 12.0.1 Safari Version 15.1 (17612.2.9.1.20) Brave Version 1.32.113 Chromium: 96.0.4664.45 (Official Build) (x86_64) 2018 MacBook Pro 13" w touchbar

I have the same issue. I have a 2018 MBP 13". Catalina 10.15.1. Alfred 4.0.6[1124]. I alternate between using only the laptop's display, a dual-monitor setup with an external display port 1920x1200 display and a single external usb-c 3440x1440 LG monitor (laptop in clamshell mode when I use this). Apart from the laptop's screen, none are 'retina' resolutions. So I guess a complicated setup and it does cause problems with other apps too when I switch between setups. The problem is that it's relatively sporadic - it happens perhaps 2-3 times per week. As above, it appears like a window management problem since I can still type something and Alfred will 'action' it - I just can't see what I'm doing. If I quit and restart Alfred it reappears as expected. I'll try 'Compatibility mode' for windowing to see if that helps.