Error with Ledger Nano S Plus - not able to sign for Polkadot.js web extension

polkadot-js / extension

Simple browser extension for managing Polkadot and Substrate network accounts in a browser. Allows the signing of extrinsics using these accounts. Also provides a simple interface for compliant extensions for dapps.

Apache License 2.0

965 stars 403 forks source link

Error with Ledger Nano S Plus - not able to sign for Polkadot.js web extension #1326

Closed rgroener closed 3 months ago

rgroener commented 3 months ago

I'm submitting a ...

[ ] Bug report
[ ] Feature request
[X] Support request
[ ] Other

What is the current behavior and expected behavior? Signing transactions with Ledger Nano S not possible anymore. Worked fine until last week. Error-Message when trying to sign via the polkadot.js extension:

Ledger error: Failed to execute 'requestDevice' on 'USB': Must be handling a user gesture to show a permission request.

**Please tell us about your environment:***

OS: Linux (Arch) Browser: Chrome (Version 122.0.6261.94 (Official Build) (64-bit)) App and Firmware on Ledger Nano S are up to date. (Updated after the error occurred, therefore the new app/fw version should not be the problem...)

Interacting with Ledger-Live works normal. To me, it seems to be a problem with the polkadot.js extension.

On a different device, the same error is showing up.

Thanks in advance...

Tbaut commented 3 months ago

Thanks a lot for the report @rgroener, I'll try to reproduce shortly. Can you tell whether this is working fine with another extension such as Talisman?

rgroener commented 3 months ago

@Tbaut, thanks for your fast response. I found a solution in the meantime. I had to "open the extension in new window" and was then able to connect and sign the transaction.

I have no idea, what triggered this behavior...

I found the workaround on stackexchange.com https://substrate.stackexchange.com/questions/2028/issues-with-ledger-nano-s-plus-not-able-to-sign-for-polkadot-js-web-extension

Thanks for your support

Tbaut commented 3 months ago

Thank you so much for posting the workaround. This definitely sounds like a glitch in the detection lib. While we are only importing here, I'll close this issue but we can re-open if there are more occurrences of this happening in the wild.

rgroener commented 3 months ago

Great service, thanks a lot!

polkadot-js-bot commented 3 months ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.