[bug] WalletConnect + MetaMask does not reconnect on page refresh

[javamonn]

Is there an existing issue for this?

• I have searched the existing issues

Package Version

0.2.9

Current Behavior

When using the autoConnect prop on the Provider, if a user connects via Wallet Connect using MetaMask (I did not test other Wallet Connect clients) and refreshes the page, the user appears connected from the perspective of wagmi (useAccount) returns an address, but actions involving the user's wallet will fail. Specifically, prompting a signature with useSignMessage seems to send a message across the Wallet Connect bridge and displays within the user's wallet, but never resolves in wagmi. Prompting a transaction with useTransaction calcuates gas, but does not display the transaction within the user's wallet.

Expected Behavior

After connecting via Wallet Connect and refreshing the page, the user remains connected and is able to complete actions with their wallet.

Steps To Reproduce

1. Connect using Wallet Connect
2. Refresh the page, have autoConnect set on wagmi provider
3. Attempt to use useTransaction or useSignMessage

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

No response

[tmm]

Was able to confirm this issue with Rainbow using the demo in the Sign Message guide. This doesn't happen with the MM or WalletLink connectors.

Seems related to this WalletConnect/walletconnect-monorepo#718

[javamonn]

Agree that the issue on walletconnect looks to be the cause, thanks for flagging that. Not sure if you want to close this in favor of the upstream issue or leave this open to track.

[github-actions]

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 other comments you can create a new discussion.