[Bug]: Batch request error smartTransaction:showSmartTransactionStatusPage

[Pasha8914]

Describe the bug

When sending a batch of transaction requests, an error occurs on the second transaction. However, the transaction is mined successfully.

Expected behavior

When sending a batch of transaction requests, it should be processed without errors, and the transaction hash must be returned

Screenshots/Recordings

https://github.com/user-attachments/assets/83ead1f5-5590-44a7-b021-eb0a3acb9140

Steps to reproduce

1. Run project
2. Click Send self-tx
3. Sign first transaction
4. Sign second transaction as soon as the signature button is unlocked.

Error messages or log output

Request of type 'smartTransaction:showSmartTransactionStatusPage' already pending for origin chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn. Please wait.

Version

11.16.14

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

• The functionality of services that send a large number of consecutive transactions is blocked, making the services unusable.
• An error will appear in the interface, but the transaction will actually be sent, which may result in a loss of funds for the user.

[forest-diggs-consensys]

This is fixed in v12, though a transaction hash is only returned once a transaction is finalized. For context, this is to account for the case of dropped/automatically cancelled transactions (ie. if we detect a transaction would revert). This case is handled the same as if a user rejected the first transaction. Following that, the user will be able to confirm the 2nd queued transaction.

[Pasha8914]

This is fixed in v12, though a transaction hash is only returned once a transaction is finalized. For context, this is to account for the case of dropped/automatically cancelled transactions (ie. if we detect a transaction would revert). This case is handled the same as if a user rejected the first transaction. Following that, the user will be able to confirm the 2nd queued transaction.

when to expect the release of version 12