Closed matejkriz closed 1 year ago
Based on the logs and the picture, the hidapi layer (that is there "just" for very very old devices) is somehow catching the new device
Can you try to merge this and send the log again? It seems there is no detailed logging for hidapi layer
the PR log might actually be leaking some private info so better not to actually merge it... just please send here the log that it produces
The bug will be somewhere there with the HID matching logic. But any fix would need to be re-tested with old HID devices on Mac and Windows to make sure it doesn't break something (not Linux, that is not using HIDAPI)
I think the easy fix would be to just remove the trezor2:=...
; it doesn't use HID anyway. No idea why the new macos started showing it in the list now; maybe some combination of macos behaviour and hidapi code behaviour
@trezor/qa please check PR description for notes for testing https://github.com/trezor/trezor-suite/pull/8100
QA OK
tested and released to 23.4.2
Info:
Bridge 2.0.32 macOS 13.3.0/13.3.1
connect just one device (no matter if model T or model One)
check status page http://127.0.0.1:21325/status/
Expected:
Actual:
detailed logs: log (1).gz