-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ledger "unexpected application error!" after clicking the account to connect with "No LedgerRequestKeysContext found" #4786
Comments
How about for edge browser? |
Did not work with edge browser got the same error message |
@314159265359879 I've tried reproducing the error but i didn't get any result. What version did you get this error on? Can you, please, try reproducing it on the dev branch now? Note: you won't be able to see it in the video, but i disconnected the ledger device right after signing in into leather with stacks app. reproductionAttemptLedgerError.mov |
???? Dev branch Sent from my iPhoneOn Jan 24, 2024, at 5:12 AM, Edgar Khanzadian ***@***.***> wrote:
@314159265359879 I've tried reproducing the error but i didn't get any result. What version did you get this error on? Can you, please, try reproducing it on the dev branch now?
Note: you won't be able to see it in the video, but i disconnected the ledger device right after signing in into leather with stacks app.
https://github.com/leather-wallet/extension/assets/22010816/74ceb7b4-9449-4ce7-85a8-98f6d9f82f22
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
I give up If I used a different ledger device would that make a difference? Sent from my iPhoneOn Jan 24, 2024, at 5:12 AM, Edgar Khanzadian ***@***.***> wrote:
@314159265359879 I've tried reproducing the error but i didn't get any result. What version did you get this error on? Can you, please, try reproducing it on the dev branch now?
Note: you won't be able to see it in the video, but i disconnected the ledger device right after signing in into leather with stacks app.
https://github.com/leather-wallet/extension/assets/22010816/74ceb7b4-9449-4ce7-85a8-98f6d9f82f22
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
@wizard1786 using a different ledger device shouldn't make a difference in theory, but let me know if you are able to reproduce it on another type of device. I was unable to repro it on ledger nano X |
@edgarkhanzadian I first tested this with version 6.22.0 of the wallet and a Nano S plus, it is still the same for me today with version 6.24.0. You're video isn't playing for me (looks like an issue with github). 2024-01-25_15-40-03.mp4 |
Nothing seems to make a difference Sent from my iPhoneOn Jan 25, 2024, at 9:42 AM, Werner ***@***.***> wrote:
@edgarkhanzadian I first tested this with version 6.22.0 of the wallet and a Nano S plus, it is still the same for me today with version 6.24.0.
Testing on Chrome version 120.0.6099.227
firmware version 1.1.1
You're video isn't playing for me (looks like an issue with github).
https://github.com/leather-wallet/extension/assets/33360391/bc4c87b4-c159-491d-b630-401a463c7143
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Tried to send an mp4 file of video , says it is too large ? how to get it to you
Connected to a different stacks website got the same error message
From: Edgar Khanzadian ***@***.***>
Sent: Thursday, January 25, 2024 4:19 AM
To: leather-wallet/extension ***@***.***>
Cc: wizard1786 ***@***.***>; Mention ***@***.***>
Subject: Re: [leather-wallet/extension] Ledger "unexpected application error!" after clicking the account to connect with "No LedgerRequestKeysContext found" (Issue #4786)
@wizard1786 <https://github.com/wizard1786> using a different ledger device shouldn't make a difference in theory, but let me know if you are able to reproduce it on another type of device. I was unable to repro it on ledger nano X
—
Reply to this email directly, view it on GitHub <#4786 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIXAWLXBMJBFL4ATSBBCDHDYQIPPPAVCNFSM6AAAAABBS35VKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZG4ZDINRUGA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AIXAWLVNZ7UI34XG4XJWBSTYQIPPPA5CNFSM6AAAAABBS35VKWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTR2QK6A.gif> Message ID: ***@***.***>
|
@wizard1786 We have enough video material, thanks for the effort though. If you keep hitting this error even when the Ledger device is connected to your computer and it is the same device used to setup your Leather wallet. I assume there is an issue with connection or cable. Try it on another device, another browser and/or with another cable to exclude any issues with those. Before signing in on a dapp, make sure your Leather wallet is on the same account you want to sign in with. Then sign in on the page. Please connect via [email protected] for further assistance if you see this persist. |
Reopening this issue, saw it happen. When trying to sign a transaction with Ledger, and the device isn't able to connect, we route to an error page (that isn't within the context so we see this error). |
This comment was marked as off-topic.
This comment was marked as off-topic.
I've been investigating this but as yet unable to reproduce. Once signed in to a DAPP with ledger, if I then disconnect, when I try and perform an action it prompts me to connect the Ledger again.
I'll keep investigating and try with a Stacks interaction instead in case there is some bug there. @kyranjamie do you remember exactly what you were doing to cause the error? Maybe its different than the device not being connected and it's an issue with communicating with a connected device? |
This was a routing issue I think, where you get routed somewhere outside the context. Try with lockstacks.com |
I could be missing something here but if my Ledger is not connected, I consistently get a prompt to ask me to connect it rather than hitting any kind of uncaught error.
If I try with
In both cases, the Leather popup handles the lack of Ledger connection gracefully and shows the Looking at the code and two places where we use
If I am testing If it is still a bug it seems likely related to
@kyranjamie : do you know what the @314159265359879 : I can't play your repro video linked in #4786 (comment). When you have time can you please help me try and reproduce this? |
Thanks for the investigation @pete-watters. Could be that it's been fixed 👍🏼 RE: |
OK thanks. I will remove that route and when Werner is back I will double check with him and if he cannot reproduce I will close. |
@314159265359879 when you have a chance can you please help test if this is still a problem? I was unable to reproduce so I think it is fixed but if you can still reproduce it please let me know |
@pete-watters I retested this too, and it looks resolved indeed. It is handled gracefully now. |
OK that's great, thanks for confirming 👍 |
## [6.39.0](v6.38.0...v6.39.0) (2024-05-14) ### Features * hide asset list unsupported tokens in accordion, closes [#16](#16) ([f37bb1b](f37bb1b)) ### Bug Fixes * add schema validation for stamps ([7a89337](7a89337)) * change default to pulling 10 keys ([b5c9c79](b5c9c79)) * compliance checks reenabled ([d0c17ec](d0c17ec)) * constant retrying of metadata ([540c349](540c349)) * double stacks asset in ledger mode ([5d9895f](5d9895f)) * remove ledger add more keys route, ref [#4786](#4786) ([45c9968](45c9968)) * use nakamoto testnet link when network is set to nakamoto testnet ([e522113](e522113)) ### Internal * input calc helper methods ([16a9e6e](16a9e6e)) * post-release merge back ([9caef96](9caef96)) * remove multiple recipients components ([8f83bcc](8f83bcc))
Reproduce with these steps
To fix issue: connect Ledger Device to your computer again, start the Stacks app on the Ledger device then try again.
I think instead of this error the wallet should show better guidance for the user.
The text was updated successfully, but these errors were encountered: