Describe the bug

While having the Custom Nonce settings enabled, if I queue 2 transactions and confirm the first one, I can see how the nonce for the 2nd transaction is never updated.

Expected behavior

Same as in prod? The nonce is updated after confirming the first transaction

Screenshots/Recordings

In the first part of the video you see the issue, in the second part, you see how it's the behaviour currently in production 12.3.1

Steps to reproduce

1. Go to Advanced Settings
2. Enable Custom nonce
3. Go to the test dapp
4. Trigger 2 transactions
5. Confirm the first one
6. See how the second one still has the old nonce
7. Confirming the second one leads to nonce too low error

Error messages or log output

No response

Detection stage

During release testing

Version

12.5.0

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

No response