MetaMask / MetaMask/metamask-extension
[Sentry] Error: No custom network client was found with the ID "912f35c0-d795-4f55-a0b2-95f02ede3ff3".
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Sentry Issue: [METAMASK-XHJK](https://metamask.sentry.io/issues/6546002924/?referrer=github_integration)
```
Error: No custom network client was found with the ID "912f35c0-d795-4f55-a0b2-95f02ede3ff3".
at MetamaskController.setupProviderEngineEip1193 (app/scripts/metamask-controller.js:5850:38)
at MetamaskController.setupProviderConnectionEip1193 (app/scripts/metamask-controller.js:5688:25)
at MetamaskController.setupUntrustedCommunicationEip1193 (app/scripts/metamask-controller.js:5413:10)
at ge (/metamask/background-8.js:1:20660)
at me (/metamask/background-8.js:1:20541)
...
(5 additional frame(s) were not displayed)
```
Contributor guide
Research direction
Start in app/scripts/metamask-controller.js at setupUntrustedCommunicationEip1193, setupProviderConnectionEip1193, and setupProviderEngineEip1193, then compare the Sentry stack with the custom network client lookup. Reproduce the affected provider-connection flow if possible and establish why the reported client ID is unavailable; done means the failure is resolved or its expected handling is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100