MK
MK
@DanielSinclair I can look into refactoring the tests and suspress those warnings in another PR ? Apparently those warnings were already there since the `@testing-library/jest-dom` wants us to use their...
@SocketSecurity ignore-all
@LufyCZ Thanks for raising this issue. We'll look into how we can tree shake the components when they are not used 👍
Will try to do this on the appkit level
This is fixed in the latest release. I'll close this issue for now, but please let me know if you're still able to reproduce.
@josadcha Looking into this now
I'm able to reproduce this as well. Reporting this to the wagmi team to see what's going on.
Seems like this is a EIP-1193 and EIP-6963 issue. We should be deprecating EIP-1193 pretty soon and fix this. I'll keep this issue open meanwhile 👍
@babkenmes We have `metaMaskWallet` EIP-1193 and EIP-6963 connector which shares the same `window.ethereum` instance, that's why it throws that error since it's marked as already "connected" from Wagmi. Feel free...
Here is another EIP-1193 bug we've encountered https://github.com/wevm/wagmi/issues/3606. As i said all these EIP-1193 breaking behaviours should be resolved once we migrate fully over to EIP-6963.