Bug Report: Fail to sign multiple transactions consecutively

[ColinWttt]

Bug: When signing multiple transactions in succession manually, the second and subsequent transactions fail after signing. After some time, I am able to successfully sign transactions.

This error can be reproduced on snaps.consensys.net/starknet, when you send tokens consecutively, the second one fails.

console log two types of errors randomly
error1: MetaMask - RPC Error: 59: A transaction with the same hash already exists in the mempool

error2: MetaMask - RPC Error: 52: Invalid transaction nonce

starknet-snap version: @consensys/starknet-snap 2.2.0

MetaMask version: 11.0.0

Chrome: 117.0.5938.92 (arm 64)

Network: Starknet Goerli Testnet

[stanleyyconsensys]

the issue was introduced when the transaction has sent, but it is still pending at the block, hence the latest block nonce is not updated on chain.

when we send another transaction in between the nonce update, it will occur such issue

we can resolve the issue by
Opt1 : adding a wait for transaction to block the UI
Opt2 : increment the nonce by adding a memory store to remember the last nonce from snap
Opt3 : retry the request with nonce increment when it has nonce error

[vivek-consensys]

Tested the fix by @khanti42 on dev and the user is able to sign multiple transactions consecutively.