VIA 3.0.0 desktop app fails to detect ZUOYA GMK87 keyboard on macOS Sequoia, while web version partially works but can't fully interact

[Arzangulyan]

Describe the bug
The VIA desktop application for macOS (version 3.0.0) does not detect the ZUOYA GMK87 keyboard when connected to a MacBook Air M3 running macOS Sequoia 15.0.1. The web version of VIA (usevia.app) detects the keyboard and shows an "Authorize Device" button, but after authorization, it cannot interact with the keyboard.

To Reproduce

1. Connect ZUOYA GMK87 keyboard to MacBook Air M3 via USB
2. Open VIA desktop application (version 3.0.0)
3. Observe that the application does not detect the keyboard
4. Go to https://usevia.app/ in Chrome browser
5. Click "Authorize device" button
6. Select ZUOYA GMK87 from the Chrome modal window
7. Observe that Chrome shows the keyboard as connected
8. Attempt to interact with the keyboard through the web interface
9. Note that VIA cannot interact with the keyboard despite being connected

Expected behavior
Both the VIA desktop application and web interface should detect the ZUOYA GMK87 keyboard, allow authorization, and enable full interaction for customization and configuration.

Screenshots
[You may want to attach the screenshots you provided earlier]

VIA Version

• I am using https://usevia.app/
• I am using the latest release of the desktop app from https://github.com/the-via/releases/releases/latest

Keyboard firmware VIA protocol
unknown

Desktop (please complete the following information):

• OS: macOS Sequoia 15.0.1
• Browser: Chrome

Custom json definition?

• I am loading a custom json definition using the designer tab

Sanity checks

• I have tried connecting the keyboard directly to the computer (i.e. not using a USB hub)
• I have flashed the latest firmware from https://www.caniusevia.com/docs/download_firmware

Additional context
The issue appears to be related to compatibility between the VIA desktop application and macOS Sequoia. The web interface partially works but cannot fully interact with the keyboard. This suggests a potential issue with driver compatibility or permissions in the new macOS version. The desktop application may require an update to support macOS Sequoia fully.