[Bug]: Signed transaction in custom testnet network (and probably other mainnet networks) blocks transactions on all other networks

[farzad-eth]

Describe the bug

When using MetaMask with a custom testnet network, a signed transaction appeared in the MetaMask history for that specific custom network. This signed transaction is causing a critical issue that prevents sending transactions on all other networks, including Ethereum mainnet, Arbitrum, and other supported networks.

Expected behavior

Transactions should be able to be sent on all networks independently, regardless of activity on custom testnet networks.

Screenshots/Recordings

Steps to reproduce

Add a custom testnet network to MetaMask
Perform a transaction on the custom testnet network
Observe a signed transaction in the MetaMask history for the custom network
Attempt to send transactions on other networks (e.g., Ethereum mainnet, Arbitrum)

Error messages or log output

No response

Detection stage

In production (default)

Version

12.0.6

Build type

None

Browser

Chrome, Brave

Operating system

Windows

Hardware wallet

No response

Additional context

The only way to resolve this issue is to manually clear the activity tab data for each network individually, including all custom and main networks. This process is time-consuming and frustrating for users.

Severity

High - This issue significantly impairs core functionality and affects all networks.

[bschorchit]

Thank you for your report @farzad-eth ! I'm closing this as we're tracking this issue here #23361. We'll be releasing a fix on our next release (v12.3)