Skip to content

Conversation

@mahmud-bn
Copy link
Contributor

Description

PR in response to Issue #1076

Checklist

  • The version field in package.json is incremented following semantic versioning
  • The box that allows repo maintainers to update this PR is checked
  • I tested locally to make sure this feature/fix works
  • This PR passes the Circle CI checks

Copy link
Contributor

@taylorjdawson taylorjdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we bump walletconnect in the demo package.json as well to 2.0.4-alpha.2

@mahmud-bn mahmud-bn merged commit 7c80e49 into v2-web3-onboard-develop Jun 27, 2022
@mahmud-bn mahmud-bn deleted the feature/walletConnect-chain-request branch June 27, 2022 22:27
This was referenced Jun 28, 2022
@ArshiaDhiman
Copy link

Having issues with WalletConnect not connecting to the first ChainId specified. I upgraded WalletConnect module and used this

const wallet_connect = walletConnectModule({ connectFirstChainId: true });

Is there anything I am missing to fix the issue of providing the correct chain when connecting?

Thanks 😄

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants