1921153 - Cannot connect to Ledger in Temple Wallet with Firefox Nightly

Status: UNCONFIRMED

(WebExtensions :: Untriaged, defect)

Description

[leotreasure]

Attachment: Screenshot 2024-09-26 at 12.35.36 pm.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:132.0) Gecko/20100101 Firefox/132.0

Steps to reproduce:

Install the Temple Wallet extension
Set up wallet
Connect Ledger

Actual results:

The option to choose Ledger did not appear in the list of options

Expected results:

The option to choose Ledger should have appeared in the list of options

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Alex Cornestean]

Hello,

I’m from Webextensions QA and I’m attempting to reproduce the issue, but the step “Connect Ledger” is not clear to me as I’m not entirely familiar with crypto wallets.
Is the “Ledger” you are mentioning the “Ledger hardware wallet” (https://shop.ledger.com/#category-cryptocurrency-wallets) or is there an app alternative? If it’s the first, I do not own one so I will not be able to reproduce the issue. If there is an app alternative, please let me know.

Thank you !

Comment 3

[leotreasure]

Hi! Thanks for taking a look at this. You should be anle to simulate the device.

https://developers.ledger.com/docs/discover/wallet-api/simulator/introduction

Comment 4

[Alex Cornestean]

(In reply to leotreasure from comment #3)

Hi! Thanks for taking a look at this. You should be anle to simulate the device.

https://developers.ledger.com/docs/discover/wallet-api/simulator/introduction

Hello and thank you for the link !

I tried following the guide to install/configure the simulator but unfortunately, I cannot piece together the information to actually set it up.
I did a bit of searching and found emulators for the Ledger devices (https://github.com/LedgerHQ/speculos and https://www.npmjs.com/package/@ledgerhq/wallet-api-simulator?activeTab=readme), however, I hit errors and lack of permissions when trying to set them up, once more.

I’ll NeedInfo one of our devs who’ll manage to make sense of the information relayed in those guides and hopefully manage to set up one of those simulators/emulators.

Comment 5

[Luca Greco [:rpl] [:luca] [:lgreco]]

This issue in the TempleWallet github repo https://github.com/madfish-solutions/templewallet-extension/issues/889 seems to suggest that a change on the Ledger Live side may have disabled a websocket interface in favor of reaching the hardware walled through WebHID instead.
Firefox doesn't support WebHID API (see MDN compat table here) and so I can't exclude that change on the Ledger Live side to be part of why it is not listed in the extensions options anymore, but I don't have enough details to be able to confirm if that is actually the reason behind this issue.

I took a look to the older versions changelogs listed from https://addons.mozilla.org/en-US/firefox/addon/temple-wallet/versions/ and I noticed the following note which may also be relevant:

Version 1.19.2 (Released Released Dec 11, 2023)
...

• Ledger Live connection is no longer available

I'd suggest to report the issue to the extension issue tracker here: https://github.com/madfish-solutions/templewallet-extension/issues
The extensions developers may help to confim the issue and help to gather more details useful to investigate it on the Firefox side (if it turns out to be due to a change on the Firefox side to have introduced the issue for the extensions).

Alternatively if the reporter is able to confirm on their local setup that the last version of the TempleWallet extension still works on a previous Firefox version and it did regress in more recent Firefox Nightly versions, then if the reporter could try to bisect the regressing change using mozregression tool (https://mozilla.github.io/mozregression/), that may be giving us some useful pointers to make this issue actionable.

:leotreasure, would you mind to report the issue to the extension developers (through the issue tracker linked right above) and/or to try to bisect the regressing change using mozregression tool (also linked right above)?