[Bug]: Unable to add additional RPC connections when chainId=0x1

[sambacha]

Describe the bug

ON metamask flask I am unable to add any RPC connections that service mainnet ethereum (i.e. chainid=0x1)

How am I suppose to develop snaps/flasks If I can't even change to a custom RPC provider?

Steps to reproduce

1. use metamask flasks
2. try and add any rpc provider other thhan default for mainnet eth
3. congrats ur there.

Error messages or log output

No response

Version

10.11.4

Build type

Flask

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

If metamask wants to keep developers engaged, please do not regress in features. First it was the gas pricing page, now this.

[mikeyb]

This is a super annoying UI change. I want to use a local node as my RPC provider but metamask won't allow it now. Please fix this ASAP, I don't want to use trashy rpc endpoints.

[sambacha]

This is a super annoying UI change. I want to use a local node as my RPC provider but metamask won't allow it now. Please fix this ASAP, I don't want to use trashy rpc endpoints.

#10290

This is a low priority for metamask, do not expect anything to come soon with regards to this issue

[adonesky1]

@sambacha and @mikeyb when you attempt to add these alternative RPC endpoints as custom networks you will need to add a Currency Symbol on the add network form. If you do so the save button should be enabled:

Screen.Recording.2022-08-16.at.5.12.20.PM.mov

Let us know if this doesn't resolve the issue

[sambacha]

@sambacha and @mikeyb when you attempt to add these alternative RPC endpoints as custom networks you will need to add a Currency Symbol on the add network form. If you do so the save button should be enabled:

Screen.Recording.2022-08-16.at.5.12.20.PM.mov

Let us know if this doesn't resolve the issue

What release has this fix?

[adonesky1]

What release has this fix?

Did you try this on whatever version you experienced the issue?

I think the issue is that you may not have entered a Currency Symbol

[adonesky1]

I was not able to reproduce the issue you describe on the latest Flask Build on Chrome (10.18.0). If you enter valid inputs for all the fields in the add network form that are not marked optional the form should allow you to save the network successfully.

[adonesky1]

@sambacha and @mikeyb can you confirm that this fixed your issue? If so I would like to close this ticket.