Skip to content

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jeetparikh
Copy link
Contributor

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.

@jeetparikh jeetparikh requested a review from a team as a code owner June 5, 2025 07:02
// 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) {
Copy link
Contributor Author

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

Copy link

nx-cloud bot commented Jun 5, 2025

View your CI Pipeline Execution ↗ for commit 11e7b27.

Command Status Duration Result
nx affected -t build,lint,test ✅ Succeeded 2m 24s View ↗
nx run-many -p @imtbl/sdk,@imtbl/checkout-widge... ✅ Succeeded 1m 11s View ↗

☁️ Nx Cloud last updated this comment at 2025-06-05 07:05:30 UTC

@@ -218,20 +218,14 @@ export function WalletList(props: WalletListProps) {
const browserProvider = new WrappedBrowserProvider(ethereumProvider);
selectBrowserProvider(browserProvider, 'walletconnect');
Copy link
Contributor

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?

Copy link
Contributor

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) {
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants