You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked there isn't already an issue for the bug I encountered.
Describe the bug
When I use a mobile browser and Metamask I cannot switch chains. Sometimes the first time works and sometimes it doesn't. Also often when it does work I get an error: error: missing or invalid. emit() chainId: eip155:56
I have tried multiple webapps using this wagmi and it happened on all of them.
In my case I am using useSwitchChain ( const { switchChain } = useSwitchChain(); )
Link to Minimal Reproducible Example
No response
Steps To Reproduce
use a mobile chrome browser and connect wallet to a website using wagmi / wagmi web3 modal
try to switch chains
What Wagmi package(s) are you using?
wagmi
Wagmi Package(s) Version(s)
2.12.5
Viem Version
2.19.6
TypeScript Version
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
This issue has been locked since it has been closed for more than 14 days.
If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Wagmi version. If you have any questions or comments you can create a new discussion thread.
Check existing issues
Describe the bug
When I use a mobile browser and Metamask I cannot switch chains. Sometimes the first time works and sometimes it doesn't. Also often when it does work I get an error: error: missing or invalid. emit() chainId: eip155:56
I have tried multiple webapps using this wagmi and it happened on all of them.
In my case I am using useSwitchChain ( const { switchChain } = useSwitchChain(); )
Link to Minimal Reproducible Example
No response
Steps To Reproduce
What Wagmi package(s) are you using?
wagmi
Wagmi Package(s) Version(s)
2.12.5
Viem Version
2.19.6
TypeScript Version
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: