Media Keys on MacOS

[aluedtke7]

I now have a MacBookPro 2023 and the Media Keys don't work in my Flutter App. So far I only tested the built in keyboard (the keys above F7, F8 and F9).
I have set the keyboard to use the F keys directly. When I want play the next song, I press <fn> + <F9>. Maybe that makes a difference for you. When I debugPrint() the received key data in the listener, I can see a printed line for every key stroke, except for the keys where the fn key is needed/used.

Hope this helps to locate the issue.

Thanks

[localcc]

This might take a bit longer to debug for me, as I currently don't have a mac device to test this on. My suspicion for why it's not working, is that the key remapping table for MacOS->Windows keycodes is not complete and doesn't work correctly for media keys.

[aluedtke7]

If I could help, just let me know.
I was wondering, why there^s no key event when I keep the fn key pressed while pressing the other keys.

[aluedtke7]

Short update: when I configure the keyboard to use the media keys directly (without pressing fn) the app behaves the same. I think a different mapping is necessary.

[localcc]

This bug should've been fixed in 2.0.0 version of the library, it would be great if you could test it and see if it doesn't occur for you anymore.

[aluedtke7]

Hi and thank you for the update!
I made a quick test on MacOS. It's working as expected, but only in the debug version. When I compile a release version, it doesn't react on the media keys I'm using.
Funny.
Do you have a clue?

[localcc]

Have you tried to remove the app from the accessibility settings and then launching the release version, granting access and restarting it?

[aluedtke7]

I tried your suggestions and now my App reacts on the media keys!
Thanks again!

I now have to find the different logical key names (MacBook keyboard vs. Logi Keys MX).

[aluedtke7]

Sorry I was a bit too eager:
I tried my App on Linux and there the keys dont't work anymore. In my app I have this statement in the listener:
debugPrint('logicalKey ${event.data.logicalKey}');
When I press the media keys previous, play/pause and next, I get these debug printouts:

flutter: logicalKey LogicalKeyboardKey#d2818(keyId: "0x15000000ad", keyLabel: "", debugName: "Key with ID 0x015000000ad")
flutter: logicalKey LogicalKeyboardKey#dc5c9(keyId: "0x15000000ac", keyLabel: "", debugName: "Key with ID 0x015000000ac")
flutter: logicalKey LogicalKeyboardKey#df2be(keyId: "0x15000000ab", keyLabel: "", debugName: "Key with ID 0x015000000ab")

On MacOS I see the correct names like mediaFastForward/mediaTrackNext etc.

Do I need to check for different KeyNames on different OS?

[localcc]

Don't check for key names as those fail on Linux for some reason, just do a event.logicalKey == LogicalKeyboardKey.mediaPlayPause, that should work on every platform

[aluedtke7]

That's what I'm using. Here is the code:

  void listener(RawKeyEvent event) {
    if (event is RawKeyUpEvent) {
      debugPrint('logicalKey ${event.logicalKey}');
      if (event.logicalKey == LogicalKeyboardKey.mediaFastForward ||
          event.logicalKey == LogicalKeyboardKey.mediaTrackNext) {
        debugPrint('HID next track');
      } else if (event.logicalKey == LogicalKeyboardKey.mediaRewind ||
          event.logicalKey == LogicalKeyboardKey.mediaTrackPrevious) {
        debugPrint('HID prev track');
      } else if (event.logicalKey == LogicalKeyboardKey.mediaPlayPause) {
        debugPrint('HID play pause');
      }
    }
  }

With this code, I get these outputs on Linux:

flutter: logicalKey LogicalKeyboardKey#d2818(keyId: "0x15000000ad", keyLabel: "", debugName: "Key with ID 0x015000000ad")
flutter: logicalKey LogicalKeyboardKey#dc5c9(keyId: "0x15000000ac", keyLabel: "", debugName: "Key with ID 0x015000000ac")
flutter: logicalKey LogicalKeyboardKey#df2be(keyId: "0x15000000ab", keyLabel: "", debugName: "Key with ID 0x015000000ab")

On Linux I don't see a KeyLabel or a meaningful debugName in the key data. On MacOS I get meaningful Key names and the code works as expected.

[localcc]

Huh that's weird, I'll give you an update regarding the fix in the morning

[aluedtke7]

No hurry needed! I can test on Linux soonest on Sunday.