Flyshewoorst

Nope, clean setup. Fewer applications than before.

Hello, I've bought a new Mac recently and I'm still getting this error without having configured any Shortcut within System Preferences (so everything is set to default, "ab Werk", as we are used to say in Germany).

Yes, I need to record and display whole sequences of keys, including active modifiers. Could it be that only QWERTZ-Keyboards are affected? By the way: It shouldn't matter if I'm using a local monitor or not. Alfred seems to break local monitors, and that shouldn't be the case. How? By following the steps I described? Why? Alfred affects third party applications in a way that is not intended. How is this not a bug?

I get that you guys don't do it by intention (why would you?), but I definitely notice a change with Alfred running and without having it running. Sure thing. 1: Create a new Cocoa project (I'm using Swift here, but shouldn't make a difference). 2: Replace the ViewController.swift's code with: import Cocoa class ViewController: NSViewController { override func viewDidLoad() { super.viewDidLoad() NSEvent.addLocalMonitorForEvents(matching: [.keyUp, .keyDown, .flagsChanged], handler: onKeyEvent) // Do any additional setup after loading the view. } private func onKeyEvent(_ event: NSEvent) -> NSEvent? { print(event.keyCode) return event } override var representedObject: Any? { didSet { // Update the view, if already loaded. } } } 3: Observe console output when Alfred is running and when it is not running. Use CMD + ALT + \ (Key with keycode 42, to be precisely) to reproduce the issue. I've made sure that it isn't BTTs fault, no other apps like Karabiner or Keyboard Maestro are installed.

Just to make sure: My point is that the key code of the locally observed event is changed from 42 to 8 when Alfred is running and the ALT and CMD modifiers are active, keyboard informations have been added for the sake of completeness.

As a developer, I'm using Alfred myself a lot. While I was working on my own little private project, I've noticed a very strange behaviour when Alfred 3.8 is running. It unfortunately breaks my application by altering the key code of NSEvent/CGEvents of type keyDown and keyUp observed by a local event monitor. I'm using a local event monitor and a global monitor with the .headInsertEventTap option to observe events of type .keyDown, .keyUp and .flagsChanged within my application. The two are used for completely different purposes and only one of them is active at a time. While the debug output of the global monitor always yields correct key codes, the local monitor does not under the following circumstances: - The key with key code 42 is pressed (# on QWERTZ-keyboards) - The modifier flags ALT and CMD are active If the above conditions are met, the key code is changed to 8, which is C on QWERTZ-keyboards. Turning off Alfred prevents this from happening. I've made sure to disable all power pack workflows. Issue occurs in MacOs 10.14 - 10.14.3.