[Bug]: Adding custom RPC URL results in 'Error: No custom network client was found with the ID'

sleepytanya commented 4 months ago

Describe the bug

Adding another RPC URL for the existing chain results in 'Error: No custom network client was found with the ID'. URL is successfully replaced, transactions can be submitted as expected.

Unable to change RPC URL back to https://network*name-mainnet.infura.io, error 'Couldn't fetch chain id':

Error when adding cutom RPC for Polygon:

Bug is present in the latest v12.0.0, on develop and in 12.1.0

Expected behavior

-

Screenshots/Recordings

https://github.com/user-attachments/assets/16389ede-996c-40e1-b19a-166bd302e90d

Steps to reproduce

Go to Setting -> Networks
Add alternative RPC URL for the existing chain

Error messages or log output

No response

Detection stage

In production (default)

Version

v12.0.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

Gudahtt commented 3 months ago

I don't think https://avalanche-mainnet.infura.io is a valid URL, the project ID is missing. So "Could not fetch chain ID" is the correct error in that case.

Not sure about that first error though.

salimtb commented 3 months ago

hey @sleepytanya , the URL https://avalanche-mainnet.infura.io is not a valid RPC URL , like @Gudahtt said the project ID is missing. regarding the second Error on polygon , can you pls share the RPC URL used ?

sleepytanya commented 3 months ago

@Gudahtt @salimtb

Here is RPC I used for Polygon https://polygon-mainnet.public.blastapi.io Seems like it happens with different RPC URLs on different chains, not Polygon only.

https://github.com/user-attachments/assets/79103278-b5d8-4508-ac6e-795ef1253e42

Network details showing wrong / incomplete link?