Open 0x70b1a5 opened 2 years ago
+1 Same problem here
@0x70b1a5 Does login work for you with Trezor Bridge? Or running Trezor Suite in the background.
@sime Unfortunately, it does not work with either method. With Suite in the background, attempting to connect via Firefox DOES actually open a new tab and set the Trezor to "In Use" in Suite, but it never connects to my app.
@0x70b1a5 Not sure what you are experiencing now, you don't need to set the Trezor to 'in use' in the suite, you only need to have Trezor Suite running.
To confirm the bridge is running, visit http://127.0.0.1:21325/status/
Can you get interactions with your Trezor to work on this site? https://connect.trezor.io/9/#/method/getPublicKey
@sime I wasn't manually setting Trezor to 'in use'; it was setting itself to 'in use' as soon as my local web app tried to authenticate with Trezor.
The bridge is running, yes.
In firefox, trezor works fine with connect.trezor.io, yes. Interesting! Is that website using the v9 API?
In firefox, trezor works fine with connect.trezor.io, yes. Interesting! Is that website using the v9 API?
Yes, note the '9' in the URL https://connect.trezor.io/9/
Alright, cool. However, for some reason I still can't authenticate with Firefox using trezor/connect-web from my local React app. Using Brave browser, it works fine.
@0x70b1a5 Could be related to this issue: https://github.com/trezor/trezor-suite/issues/5644
Try disabling cookie protection.
Describe the bug Connect-web v9 does not work in Firefox because FF does not support the WebUSB api, via the experimental
Feature-Policy: usb
.Info:
How to reproduce Steps to reproduce the behavior:
npx create-react-app trezor-ff-bug; cd trezor-ff-bug
App.js
npm run start
localhost:3000
, open devtools with F12Feature Policy: Skipping unsupported feature name “usb”.
and note that any Trezor functionality (eg, a button that calls the login function) doesn't work.Expected behavior I expected to be able to use trezor v9 in Firefox, which is a popular modern browser.