web3modal: [bug] useWeb3Modal 4.1.1

Link to minimal reproducible example

web3Modal 4.1.1 is buggy

Summary

Hello team,

So basically i just update to latest web3modal

"@web3modal/wagmi": "^4.1.1",
"viem": "^2.8.13",
"wagmi": "^2.5.11"

I found out that await open({ view: 'Networks' }) doesn’t want to switch to selected network, it just navigate to connect wallet again, the page need to be refresh in order to make it work.

if I am using legacy version

npm install @web3modal/wagmi wagmi@1.4.13 viem@1.21.4 --legacy-peer-deps

it is working fine

fyi, no code changes apart from different method and setup when integrate with latest version.

Is there anything I am missing? Is there away to switch to selected network without refresh?

evidence:

4.1.1 https://github.com/WalletConnect/web3modal/assets/26643922/39980e21-cbf1-4e44-929d-39cd2afa3c30

3.5.7 https://github.com/WalletConnect/web3modal/assets/26643922/969d7ce0-69bb-4a25-995b-a02fc494ea91

List of related npm package versions

@web3modal/wagmi”: “^4.1.1”, “viem”: “^2.8.13”, “wagmi”: “^2.5.11”

About this issue

  • Original URL
  • State: closed
  • Created 3 months ago
  • Comments: 22 (8 by maintainers)

Most upvoted comments

alright, it’s fixed at 4.1.7 finally

We’ll follow up on this issue, feel free to subscribe and comment. https://github.com/WalletConnect/web3modal/issues/2126

Thanks! 👍

@nsnull0 thanks! I was able to see the last video, I was only able to reproduce this on Edge but I see some other devs are experiencing it as well, we’ll try to fix this today, as for now we know this happens when the email feature is enabled.

@glitch-txs I think i found out my problem while creating fresh new project.

2 issues resolved:

  1. I was accidentally using Web3ModalProvider at many different place, it somehow remove the account information, it need to be refreshed manually.
  2. tried again with 4.1.1 , confirmed it still got disconnection bug, which already fixed with 4.1.6

now after fix number 1, everything fixed with the latest version, working as expected seamlessly.

Thank you for the support!

Thank you for follow up the issue… I guess the fix version is from version 4.1.6… let me test on 4.1.6 soon…

@nsnull0 could you try again, this should be fixed by now

Are you able to reproduce the issue here: https://lab.web3modal.com/ Could you share steps to reproduce it if so? Thanks!