bug: Error: could not detect network (event="noNetwork", code=NETWORK_ERROR

[soccerarenadev]

Is there an existing issue for this?

• I have searched the existing issues

Package Version

0.7.5

Current Behavior

I'm constantly getting this error:

Error: could not detect network (event="noNetwork", code=NETWORK_ERROR, version=providers/5.7.1)

I have alchemyProvider as my first provider.
Changing back to the default API doesn't change anything, but removing from providers does.

However, I have also infuraProvider. But unless I remove alchemyProvider, it doesn't fallback to infureProvider.

Expected Behavior

Fallback to other providers if the first provider fails.

Steps To Reproduce

No response

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

No response

[jxom]

Thanks for reporting. This issue is temporarily closed due to lack of information. Please provide a minimal reproducible example via a CodeSandbox (feel free to use this template) and reopen this issue. It will help us reproduce your issue! 🙏

[soccerarenadev]

There you have the minimal reproducible example:
https://codesandbox.io/s/zen-browser-c5mh21?file=/pages/_app.tsx

However, it is just the rainbowkit example. Very basic stuff with little things.
Using the ethers.js API key.
However, with my own API key I have the same error.

Could you reopen it?

[paulpopus]

We're also seeing this with the Alchemy provider

[wassienabe]

I have the same issue after copy/pasting the example shown here:
https://wagmi.sh/examples/connect-wallet

Adding in the Infura provider and placing it before the Alchemy provider resolved it for now.

[adshodgson]

Also seeing this issue...

const { chains, provider, webSocketProvider } = configureChains(defaultChain, [
    infuraProvider({
        apiKey: process.env.NEXT_PUBLIC_INFURA_KEY,
        priority: 1,
    }),
    publicProvider(),
])

[github-actions]

This issue has been locked since it has been closed for more than 14 days.

If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest wagmi version. If you have any other comments you can create a new discussion.