fix(checkout-widgets): Fix WalletConnect NETWORK_ERROR on chain switch#2877
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit d5f7dec
☁️ Nx Cloud last updated this comment at |
naveen-imtb
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix
WEB3_PROVIDER_ERROR: network changedwhen connecting via WalletConnect to wallets that require a chain switch (e.g. Fireblocks vaults).Detail and impact of the change
The WC connect callback in
WalletList.tsxconstructedWrappedBrowserProvider(ethereumProvider)without the'any'network arg. Ethers pins the provider to the initial chain and throwsNETWORK_ERRORon the nextgetNetwork()call onceswitchEthereumChainflips the underlying chain. Adding'any'lets the provider track the live chain- the documented idiom for changeable networks (ethers v6 BrowserProvider docs).Anything else worth calling out?
The pattern is already applied elsewhere in widgets-lib (
convertToNetworkChangeableProvider, bridge'sWalletAndNetworkSelector)