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

fix: send not enough funds error handling at submit time #8076

Merged
merged 2 commits into from
Nov 4, 2024

Conversation

NeOMakinG
Copy link
Collaborator

Description

If you first encounter low gas fees when opening the send modal, you might have the button as valid

If you wait like 1 mins, the fast fees might be > as what you had 1 min before, but you can continue

Then an error happens (with native, it says "Error cancelled the request"), which is wrong because the TX has been cancelled due to not enough balance to pay gas fees

Issue (if applicable)

partially #8035

Risk

Low

High Risk PRs Require 2 approvals

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

Testing

  • Monkey patch in useSendDetails:
    image

  • Or, have a very low fee asset balance, like 0.005 POL for example, sometime it's enough, then sometime not, try to find the perfect time (almost impossible, I had it one time in 30 mins)

Engineering

n/a

Operations

n/a

  • 🏁 My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)

image

@NeOMakinG NeOMakinG requested a review from a team as a code owner November 4, 2024 16:38
Copy link
Member

@woodenfurniture woodenfurniture left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@woodenfurniture woodenfurniture enabled auto-merge (squash) November 4, 2024 21:02
@woodenfurniture woodenfurniture merged commit 740476f into develop Nov 4, 2024
1 check passed
@woodenfurniture woodenfurniture deleted the send-error-handling branch November 4, 2024 21:03
const feeAsset = selectFeeAssetById(store.getState(), feeAssetId ?? '')

// @TODO: as this is the first time we are handling errors from unchained in this scope, we dont have a complete error handling strategy
// If we need to handle more errors, we should create a proper error handler
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants