MetaMask / MetaMask/metamask-extension

[Bug]: Networks - No Infura network client was found with the ID "sepolia".

Open
#32,393 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-Infura regression-prod-12.16.1 Sev2-normal team-core-platform type-bug
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?

  1. Delete Sepolia network on a MM instance
  2. Re-Add Sepolia with the same infura key
  3. Connect to a dapp
  4. See everything works
  5. Switch to another MM instance from the same browser
  6. Select Sepolia
  7. Connect to the dapp
  8. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.