Intermittent "NotAllowedError: Failed to write the report." on Chrome v115+ about xkeys HOT 6 CLOSED

This is the first we have heard of. The output report has stayed the same.
It may be trying to write to the wrong end point.
The X-keys is several "devices" to the OS as it is a compound USB device.
Be sure to check the write length is longer than 20 or HID usage page 0xc (12 dec
)

Writing to device "0" for example does not always work if the OS enumerates them in a different order.

from xkeys.

This was pretty easy to reproduce, and I could see that when approving the device it returns 3 different objects where we were always taking the first of this list.

Filtering this to only return and accept ones with usagePage 12 has made the issue go away for me

from xkeys.

Correction: Issue might have been present on earlier Chrome version (115) and was exposed by a combination of Windows upgrade and Chrome update.

from xkeys.

I reviewed with our firmware engineer; she recommends:
filter only on:
VID
PID
Usage page 12
write length > 20
to get the "device" supported by this lib.
other things are redundant or not consistent over all OSs

from xkeys.

thanks guys, I'm able to fix it locally since I can access these fields.

Will update my package once #93 is merged since it seems to also take care of an uncaught promise rejection.

Won't close this issue myself until above is merged

from xkeys.

This is now fixed in version v3.0.1, thanks for contributing!

from xkeys.