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

[Bug]: Doing a single transaction with fees configured different from saved fees results in forgetting of saved fees. #16796

Open
MicahZoltu opened this issue Dec 4, 2022 · 4 comments
Labels

Comments

@MicahZoltu
Copy link

Describe the bug

I submit all of my transactions with the same max fee and priority fee, which I have configured in MetaMask's advanced gas fee UI and saved via the checkbox in that UI that allows me to remember my settings. This works great under normal conditions, but if I want to do a single transaction with different fees (e.g., higher priority fee than normal) it results in me losing my saved configuration, even though I unchecked the box to "save these fees as default".

Steps to reproduce

  1. Submit a transaction with custom fees and check the box for saving fee configuration as defaults.
  2. Submit another transaction and notice that it uses the saved fees (expected behavior).
  3. Submit a third transaction, but for this one edit the custom fees and uncheck the box to save the fees.
  4. Submit a fourth transaction and notice that it has reverted to using MetaMask recommended fees rather than the ones I saved as default in step (1).

Error messages or log output

No response

Version

10.22.2

Build type

None

Browser

Firefox

Operating system

Windows

Hardware wallet

No response

Additional context

This wouldn't be a problem except that BitPay still hasn't updated their stuff to work with EIP-1559, and their contracts are setup to hard fail if the user doesn't have a sufficiently high GAS_PRICE (effective gas price). This is incredibly frustrating and I have complained repeatedly to BitPay about it but they don't seem to care. However, since they are one of the leading payment processors, I think it is important that it is minimally painful to use them while also using MetaMask.

I think this is a legitimate bug even if not for BitPay's stupidity, I bring it up only to help with prioritization.

@bschorchit bschorchit added area-gas Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead labels Dec 5, 2022
@bschorchit
Copy link

Thank you for the detailed report, @MicahZoltu! We'll look into it :)

@bschorchit
Copy link

Sorry for the late response on this @MicahZoltu ! But we were not able to reproduce it. It might be a confusion with step 3.
You mentioned 3. Submit a third transaction, but for this one edit the custom fees and uncheck the box to save the fees. but as we've tested the checkbox auto-uncheck if you edit the values so you don't need to manually uncheck it.

Would you mind re-testing it on your side and letting us know? Thank you!

@MicahZoltu
Copy link
Author

I'm still experiencing this issue on 10.23.3.

If I have previously saved fees I see
image
If I click the "Advanced > Edit" button above the gas cost estimate I see something like this:
image
I then uncheck that box and click "Save".

Then on step 4 I see this:
image
image

@hilvmason hilvmason added team-confirmations-planning (only for internal use within Confirmations team) and removed team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead labels Jun 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 3, 2023

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

@github-actions github-actions bot added the stale issues and PRs marked as stale label Sep 3, 2023
@bschorchit bschorchit added T08-featureRequest and removed stale issues and PRs marked as stale type-bug Sev2-normal Normal severity; minor loss of service or inconvenience. labels Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants
@MicahZoltu @bschorchit @hilvmason and others