[Bug]: Error while connecting to the custom network.

[wnhedaxx]

Describe the bug

sometimes metamask does not responds it gets stucked while we try to add other chains in it.
recently i added Antimatter B2 Network in metamask it shows error.
Network name;
Antimatter B2 Network
Network URL;
https://rpc.antimatter.finance/
Chain ID;
1990
Currency symbol;
MATTER
Block explorer URL;
https://b2-explorer.antimatter.finance/

also sometimes i am not able to change network it shows error

Expected behavior

i expected it would support it

Screenshots/Recordings

Steps to reproduce

1)add network Antimatter B2 Network
Network name;
Antimatter B2 Network
Network URL;
https://rpc.antimatter.finance/
Chain ID;
1990
Currency symbol;
MATTER
Block explorer URL;
https://b2-explorer.antimatter.finance/
2) or visit https://dao.antimatter.finance/#/stake and connect wallet it does not get connected to Antimatter B2 Network
3)this error is from last few weeks i used Antimatter B2 Network and staked my tokens in network

Error messages or log output

Network name
Antimatter B2 Network
Network URL
https://rpc.antimatter.finance/
Chain ID
1990
Currency symbol
MATTER
View all details
This custom network is not recognized


We recommend that you verify the network details before proceeding.


Error while connecting to the custom network.

Version

11.5.1

Build type

None

Browser

Chrome

Operating system

Windows

Hardware wallet

Keystone

Additional context

nothing

Severity

i got frustrated while adding network to metamask but it gots stuck

[anaamolnar]

Hello, @wnhedaxx. Thanks for reporting! The team will review this as soon as they can.

[wnhedaxx]

I know it you guys will🔥

[AhmerAfzal1]

Facing same issue, when it'll resolve?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.