timeout with u2f tranport

[allemanfredi]

Hi,

I'm trying to integrate hw-app-iota with u2f transport in my app but i receive the following error even if my ledger is connected and iota is running:

Ledger device: Ledger device timeout. Ensure Ledger is plugged in and IOTA app is running

[Wollac]

There is a an issue with u2f and it is not working reliably at the moment to communicate with the Ledger device; see this for more: LedgerHQ/ledgerjs#306

It looks like Ledger HQ is proposing WebUSB as an alternative. WebUSB has been enabled in the master of the IOTA app and will be included in the next version (X and S) which is currently reviewed by Ledger HQ. If you want to try it out, you can install the development version on your Nano S or Blue (app development is not yet supported on the Nano X) by following the instructions here: https://github.com/IOTA-Ledger/blue-app-iota/blob/master/README.md#development (probably docker should be the easiest).

The transport methods can also be tested here http://iota-ledger.github.io/ledger-app-iota-demos.

Note, that this is only relevant for browser support as the Node.js libraries use HID to communicate with the Ledger and this works flawlessly on the X as well as the S.

[allemanfredi]

Thank you for your explanation! Unfortunately i would like to use U2F so i have to wait!

[Wollac]

Honestly, I've stopped closely following the u2f issue some time ago, but there have been already a few improvements by LedgerHQ: "short" calls work again (like getAppVersion should work on Firefox and Chrome)
However, I've no idea if and when all the calls are fixed, so it might be worth to explore other options like @ledgerhq/hw-transport-webusb

[Wollac]

After having done a bit more research on this issue, it turns out that the fix currently tested by LedgerHQ would require an updated SDK as well as some changes in the app. Since all those changes need to be reviewed by Ledger before the update can be published, this can take rather long.

Alternatively Ledger suggests moving to @ledgerhq/hw-transport-webhid, which is available in the latest Chrome stable release (users still have to activate an experimental flag on chrome://flags/#enable-experimental-web-platform-features). This approach even works with the current Ledger Nano app and firmware.

[allemanfredi]

Thank you very much! Let's say that as a temporary solution can go! as soon as i try it i'll let you know!

[sdfghdfh345gasfsdfh4545434hrthbfg]

Can you elaborate on how to move to ‘@ledgerhq/hw-transport-webhid’ please?

[jafri]

@Stoinkler its not a real solution for consumers as HID is behind an experimental flag in chrome.

[allemanfredi]

Are there any news about U2F bug?