search

MetaMask / metamask-extension

:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites
https://metamask.io
Other
11.83k stars 4.83k forks source link

[Bug]: Transaction function method name of replaced transaction remains even after being replaced by another transaction type #23038

Closed suspended closed 1 week ago

suspended commented 6 months ago

Describe the bug

I sent a transaction with "Unstake" function method name. After that, I replaced it with another transaction (send USDC to another address) with higher gas fee but the same nonce, yet the "Unstake" method is still displayed even though it should be "Send USDC".

Expected behavior

The replaced transaction should have an updated method name of the new transaction, not the replaced one.

Screenshots/Recordings

image

Steps to reproduce

  1. Send transaction 1 (ie. Stake, Unstake, etc.) with low gas price so it won't be mined immediately.
  2. Send transaction 2 with same nonce and higher gas price to replace transaction 1.
  3. Transaction 2 will succeed but retain the function method name of transaction 1.

Error messages or log output

No response

Version

11.9.0

Build type

None

Browser

Chrome

Operating system

Windows

Hardware wallet

No response

Additional context

No response

Severity

No response

Bullcoiner commented 6 months ago

Hi There! Thank you for reporting this, it has been assigned to the appropriate team to be looked at.

seaona commented 6 months ago

this relates to https://github.com/MetaMask/metamask-extension/issues/15632 and https://github.com/MetaMask/metamask-extension/issues/15393

github-actions[bot] commented 1 month ago

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[bot] commented 1 week ago

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.