-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[Bug]: Failing Transactions don't display a Warning anymore and set an insane amount of Gas fees #17379
Labels
PS-team
PS MM extension team issues
release-blocker
This bug is blocking the next release
team-confirmations-secure-ux
DEPRECATED: please use "team-confirmations" label instead
type-bug
Comments
seaona
changed the title
[Bug]: Failing Transactions don't display a Warning anymore and set an insane of Gas fees
[Bug]: Failing Transactions don't display a Warning anymore and set an insane amount of Gas fees
Jan 24, 2023
seaona
added
the
team-confirmations-secure-ux
DEPRECATED: please use "team-confirmations" label instead
label
Jan 24, 2023
Repro steps for no warning being shown + insane gas fee (in MM v10.23.1):
|
I am 95% sure that the root cause of this is the same as the root cause of #17377 |
@VSaric I am assigning you to this as well, because I think that it will be resolved by the same fix that resolves #17377 cc @ElvirCe Also, I am pretty sure that the problematic section of code is in
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
PS-team
PS MM extension team issues
release-blocker
This bug is blocking the next release
team-confirmations-secure-ux
DEPRECATED: please use "team-confirmations" label instead
type-bug
Describe the bug
Problem: when a tx is going to fail, it displays an insane amount of Gas fees and no warning:
We used to display a warning, like this:
Steps to reproduce
Error messages or log output
No response
Version
10.24.0
Build type
None
Browser
Chrome
Operating system
Linux
Hardware wallet
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: