-
Notifications
You must be signed in to change notification settings - Fork 33
feat(checkout): Handle network switch when using walletconnect #2649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
// walletconnect on trying to switch network, if network doesn't exist, it does not throw an error! | ||
// so the catch block below is not triggered, so we need to add the network manually | ||
// always calling addNetworkToWallet is harmless, as nothing happens if the network already exists | ||
if (provider.ethereumProvider?.isWalletConnect) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is crucial for walletconnect switch to work. Also adds a new network prompt when you don't have the network added
View your CI Pipeline Execution ↗ for commit 11e7b27.
☁️ Nx Cloud last updated this comment at |
@@ -218,20 +218,14 @@ export function WalletList(props: WalletListProps) { | |||
const browserProvider = new WrappedBrowserProvider(ethereumProvider); | |||
selectBrowserProvider(browserProvider, 'walletconnect'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to do this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never mind, I see why we do
@@ -218,20 +218,14 @@ export function WalletList(props: WalletListProps) { | |||
const browserProvider = new WrappedBrowserProvider(ethereumProvider); | |||
selectBrowserProvider(browserProvider, 'walletconnect'); | |||
|
|||
const { chainId } = await ((await browserProvider.getSigner()).provider.getNetwork()); | |||
|
|||
if (ethereumProvider.chainId !== targetChainId) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my testing, the ethereumProvider.chainId was never targetChainId - even when my MM was on the right chain
WalletConnect switch wasn't working when on the wrong network. This now forces the 'Switch network' screen requiring user to interact in order to switch the network.