[Bug]: Multichain - MetaMask unresponsive after adding and switching networks from a dapp
Describe the bug
Problem: whenever I add a netowrk from a dapp, MetaMask stays unresponsive and I see an empty error in the background. If I reload MetaMask I see how the network was not added and I remain in the previous selected network.
- This is not happening in prod 11.9.4
- Furthermore, this is not happening if I add this same network manually
- The error appears independently of having the
Select networks for each siteenabled or disabled - makes no difference
Expected behavior
MetaMask should switch networks and continue to work. I am able to do it in prod
Screenshots/Recordings
https://github.com/MetaMask/metamask-extension/assets/54408225/b838f6d1-77a8-432b-a75c-8b20341a0a7d
Steps to reproduce
- Go to chainlist https://chainlist.org/?testnets=true&search=bsc
- Connect MM
- Add a Network Binance Testnet
- Approve
- Switch networks
- Click again the MM icon--- see it's unresponsive, see error in the background
Error messages or log output
No response
Version
develop - with multichain flag
Build type
None
Browser
Chrome
Operating system
Linux
Hardware wallet
No response
Additional context
No response
Severity
No response
@seaona this is only with the request queuing toggled on right?
This does not appear to be related to send flow.
@darkwing that's correct. After investigating further with Shane and Alex, we've seen that this is the same issue as this one https://github.com/MetaMask/metamask-extension/issues/21929 which was already present before. From slack: it might be that the work on the area of queuing multichain fixes this one