Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GMK87 recognized by usevia.app in Chrome but not on the desktop. #284

Open
4 of 5 tasks
resuna opened this issue Jan 31, 2024 · 8 comments
Open
4 of 5 tasks

GMK87 recognized by usevia.app in Chrome but not on the desktop. #284

resuna opened this issue Jan 31, 2024 · 8 comments

Comments

@resuna
Copy link

resuna commented Jan 31, 2024

Describe the bug
Loading the JSON (v2) for the GMK87 works when using the usevia.app web interface in Chrome, but not when using the desktop app (3.0.0).

To Reproduce
Steps to reproduce the behavior:

  1. Open VIA desktop app
  2. Settings->Show Design Tab
  3. Design->Use V2 definitions
  4. Design->Load
  5. Select JSON file and load it
  6. Switch back to Configure
  7. "Searching for devices"
  8. Open usevia.app in Chrome
  9. Settings->Show Deign Tab
  10. Design->Use V2 definitions
  11. Design->Load
  12. Select JSON file and load it
  13. Switch back to Configure
  14. Authorize Device
  15. "Usevia.app wants to connect to a HID device" "ZUOYA GMK87"

Expected behavior
I expect steps 1-7 to produce the same result as steps 8-15.

VIA Version

Keyboard firmware VIA protocol
9

Desktop (please complete the following information):

  • Computer: Macbook Pro 14" 2021 (M1)
  • OS: Mac OS Sonoma 14.3
  • Browser (if applicable): Chrome 121.0.6167.85
  • VIA: via-nativia 3.0.0

Custom json definition?

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

Sanity checks

Additional context
I have used the VIA app successfully with a Keychron V7 and a Keychron K2 Pro

I downloaded the GMK87 JSON from https://mkb.gg/pages/download-center

@yonutz33
Copy link

yonutz33 commented Feb 8, 2024

Hello,

I have a similar issue but it’s the other way around. It works in the desktop app but not when using chrome directly.

@resuna
Copy link
Author

resuna commented Feb 8, 2024

@yonutz33 - Can you post your configuration for tracking? Computer/OS/browser/VIA version/VIA protocol/etc?

@yonutz33
Copy link

yonutz33 commented Feb 8, 2024

I take that back, now it works.
My guess is that it's something limited my installed version of Chrome (current version is 121.0.6167.161), since I have changed nothing in the configuration, but I noticed the recent update because of restart prompts from Chrome and a slight change in look.

For configuration tracking I can only give you the current version of Chrome (have no idea what the previous one was):

Desktop (please complete the following information):

Computer: Dell Latitude 5300
OS: Windows 10 Pro (22H2 Build 19045.3930)
Browser (if applicable): Chrome Version 121.0.6167.161 64 bit
VIA: https://usevia.app/ latest at the time of publish (version 3.0.0?)

@Hukha
Copy link

Hukha commented Feb 9, 2024

Same issue with the same keyboard here.

@slgta
Copy link

slgta commented Mar 4, 2024

same issue here. VIA on Chrome browser works, but the VIA app 3.0 on macOS 14.3.1 doesn't work .

Update: the VIA app start to work, I guess it is after I got VIA on the chrome browser working.

@eyeonee
Copy link

eyeonee commented Apr 2, 2024

anybody knows how to configure light on gmk87? cause i want to set static gradient and dont see any functions how to do it

@I-SMAF
Copy link

I-SMAF commented Apr 13, 2024

anybody knows how to configure light on gmk87? cause i want to set static gradient and dont see any functions how to do it

@eyeonee

tag me if u find the solution

but probably we must to re-write the via config json

@Arzangulyan
Copy link

Arzangulyan commented Oct 12, 2024

I'm trying to connect the same keyboard to my Mac with Sequoia, but the app doesn't even see it. The web interface, on the other hand, gives me a "Authorize Device" button, and it even sees the keyboard in the Chrome modal window, but after selecting it, Chrome simply shows that the keyboard is connected but Via still cannot interact with it.

Device: MacBookAir M3 with the public version of Sequoia 15.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants