MetaMask / MetaMask/metamask-extension
[Bug]: Networks - No Infura network client was found with the ID "sepolia".
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
I see the error No Infura network client was found with the ID "sepolia". and cannot trigger any transaction or signature from a dapp
Expected behavior
No response
Screenshots/Recordings
https://github.com/user-attachments/assets/41303190-025c-4d00-b160-419cbaa12786
Steps to reproduce
Below are the steps I performed. It's quite confusing as I was working with 2 different MM instances and I would have expected this error to appear at the first one. It seems like there was some connection between the 2, maybe because of the dapp?
- Delete Sepolia network on a MM instance
- Re-Add Sepolia with the same infura key
- Connect to a dapp
- See everything works
- Switch to another MM instance from the same browser
- Select Sepolia
- Connect to the dapp
- See no tx/signature can be triggered and the error appears
Error messages or log output
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
The report names no files, tests, or entry points. Start by reproducing the two-browser-instance sequence in Chrome on version 12.16.1, then trace the Sepolia network-client lookup used during dapp connections; done means the second instance can trigger transactions and signatures without the missing-client error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100