This bug happens when "smart transactions" are turned on, and multiple transactions are submitted in quick succession. The first one to be submitted will use the "smart transactions" setup as expected. But the second transaction will stall, and ultimately return an RPC error:
smartTransaction:showSmartTransactionStatusPage' already pending for origin chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn. Please wait.
Seemingly, MM does queue up this transaction as it does end up getting confirmed later on, but the application that initiated the transactions will not receive any notice of this. This causes the application that initiated the transaction to report a failed transaction
Expected behavior
I'd expect that MM returns either a failure when the transaction could not be submitted or a success response when it can be. Rather than MM returning a failure response even though the transaction does end up getting submitted.
Screenshots/Recordings
Steps to reproduce
This issue can be reproduced on any website that submits multiple transactions, such as Revoke.cash's batch revoke functionality.
Prerequisites:
Enable smart transactions in MM
Have multiple token approvals
Steps to reproduce:
Go to Revoke.cash and connect your MM wallet
Select multiple token approvals to revoke and click "Revoke selected"
Describe the bug
This bug happens when "smart transactions" are turned on, and multiple transactions are submitted in quick succession. The first one to be submitted will use the "smart transactions" setup as expected. But the second transaction will stall, and ultimately return an RPC error:
Seemingly, MM does queue up this transaction as it does end up getting confirmed later on, but the application that initiated the transactions will not receive any notice of this. This causes the application that initiated the transaction to report a failed transaction
Expected behavior
I'd expect that MM returns either a failure when the transaction could not be submitted or a success response when it can be. Rather than MM returning a failure response even though the transaction does end up getting submitted.
Screenshots/Recordings
Steps to reproduce
This issue can be reproduced on any website that submits multiple transactions, such as Revoke.cash's batch revoke functionality.
Prerequisites:
Steps to reproduce:
Error messages or log output
No response
Detection stage
In production (default)
Version
12.5.1
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response