Skip to content
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

Clicking send and then selecting Stacks leads to error (6.54.0) #5994

Open
314159265359879 opened this issue Dec 2, 2024 · 8 comments · May be fixed by #6125
Open

Clicking send and then selecting Stacks leads to error (6.54.0) #5994

314159265359879 opened this issue Dec 2, 2024 · 8 comments · May be fixed by #6125
Labels
area:send bug Functionality broken bug-p2 Critical functionality broken for few users, with no clear workarounds

Comments

@314159265359879
Copy link
Contributor

I have not yet been able to reproduce this issue. Likely caused by an unknown second factor.
Related to unreachable wallet config?

Steps to reproduce for the user:

  1. Click on the extension icon in the browser to open Leather
  2. Click Send
  3. Select Stacks
  4. See error:

Image

Console log
Image

@314159265359879 314159265359879 added area:send bug Functionality broken bug-p1 Critical functionality broken for many customers, with no clear workarounds labels Dec 2, 2024
Copy link

linear bot commented Dec 2, 2024

@pete-watters
Copy link
Contributor

I just tested this and I cannot reproduce it either.

I can't read the error message in the screenshot fully but it looks like there could have been a problem loading the fee estimates.

If it's working for us now I guess it was an intermittent issue and should be OK for the user now

@David-Jesse
Copy link

TypeError: Cannot read properties of undefined (reading 'fee')
at chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:22752:66
at Object.ti [as useMemo] (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103257:119)
at chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:106971:48
at useStxSendForm (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:22750:43)
at StxSendForm (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:22815:7)
at Nh (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103245:137)
at cj (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103281:258)
at Vk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103376:88)
at Uk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103364:389)
at Tk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103364:320)
at Ik (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103364:180)
at Nk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103355:88)
at Ek (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103357:300)
at jg (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103212:105)
at chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/61.js:103351:273

Here's the error message it keeps giving

@314159265359879
Copy link
Contributor Author

The user reported also trying to reinstall Leather on another browser (Brave after Chrome), but the issue persisted.

Issue related to? #5985

@314159265359879 314159265359879 added bug-p2 Critical functionality broken for few users, with no clear workarounds and removed bug-p1 Critical functionality broken for many customers, with no clear workarounds labels Dec 2, 2024
@kyranjamie
Copy link
Collaborator

I just tried this as well and couldn't replicate. Looking at the implementation, this could be poor async handling. The fee is read with the assumption it's there, and it could be that the fee hasn't loaded by the time at which user clicks send, or they're being 429'd.

@314159265359879
Copy link
Contributor Author

Original reporter of this issue reported this resolved.

@markmhendrickson
Copy link
Collaborator

Reopening since it's still outstanding (though intermittent) and getting fixed by #6125

@markmhendrickson markmhendrickson linked a pull request Feb 24, 2025 that will close this issue
@linear linear bot closed this as completed Feb 24, 2025
@314159265359879
Copy link
Contributor Author

This issue popped up again today:

TypeError: Cannot read properties of undefined (reading 'fee') at chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:23528:58 at Object.ti [as useMemo] (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101760:119) at chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:105474:48 at useStxSendForm (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:23526:43) at StxSendForm (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.js:23591:7) at Nh (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101748:137) at cj (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101784:258) at Vk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101879:88) at Uk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101867:389) at Tk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101867:320) at Ik (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101867:180) at Nk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101858:88) at Gk (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:101855:429) at J (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:114072:203) at MessagePort.R (chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/990.js:114073:128)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:send bug Functionality broken bug-p2 Critical functionality broken for few users, with no clear workarounds
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants