MetaMask / MetaMask/metamask-extension
[Bug]: Networks - Deleting Sepolia network throws non-stop errors `No custom network client was found with the ID`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
Deleting Sepolia network throws non-stop errors console errors: `No custom network client was found with the ID`.
This can spam Sentry.
### Expected behavior
Correctly handle deleting Sepolia network, so we don't get infinite errors
### Screenshots/Recordings
https://github.com/user-attachments/assets/b8ed33a7-041b-4887-ae99-b3b4bdf99a62
### Steps to reproduce
1. Delete Sepolia network
2. See console errors non-stop
### Error messages or log output
```shell
```
### Detection stage
In production (default)
### Version
12.16.1
### Build type
None
### Browser
Chrome
### Operating system
Linux
### Hardware wallet
_No response_
### Additional context
_No response_
### Severity
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Chrome on version 12.16.1: delete the Sepolia network and observe the repeated “No custom network client was found with the ID” errors. Trace the deletion flow and the repeated error source; done means deleting Sepolia no longer produces non-stop console errors or Sentry spam.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100