wagmi: bug: autoConnect fails to reconnect

Thanks @glitch-txs for your diagnosis / explanation, and @tmm for further clarification.

I just wanted to note that the Getting Started guide perfectly demonstrates this issue (my minimal repro follows the guide line-for-line). I think it would really help if the guide were updated to reflect a working scenario (especially since autoConnect: true is explicitly configured there).

Additionally, this behavior is a departure from v0.10.x, so I would recommend it be listed as a 1.x.x breaking change in the Migration Guide.

@tmm let me know if you agree – I would be happy to submit a PR with the above documentation improvements.

So I just tried using Wagmi for the first time, and the quick tutorial on the home page is still not updated. I came here to report the same issue. I use NextJS 13.4.2 and I thought that this was an issue with Next/React.

Here is my band aid solution:

    const { address, isConnected } = useAccount()
    const { connect } = useConnect({
      connector: new MetaMaskConnector(),
    })
    const { disconnect } = useDisconnect()

    useEffect(() => {
        const state = localStorage.getItem('walletConnectState') || '';

        if( !isConnected && state === 'true' ) connect();
    }, []);

    useEffect(() => {
        localStorage.setItem("walletConnectState", isConnected.toString());
    }, [isConnected]);

I also removed the autoConnect: true within the _app.tsx file where the createConfig is. Funny enough, this resulted in fixing the hydration issue too.

No idea why this issue is closed since the problem is still there.

@glitch-txs is correct! Since the connector doesn’t have storage defined, it can’t read from and write to storage. The easiest way to set up the storage property for connectors is to “register” them with the config through createConfig. Alternatively, you can call connector.setStorage to set things up. We’ll work on a better API and documentation for the latter case in a future version.

Hi guys! I think I found the issue in this PR: https://github.com/kenkunz/wagmi-autoconnect-repro/pull/1

let me explain what I see, connectors are constructed with an empty storage property, the function createConfig takes connectors as arguments and add them a customized storage which is the one the connector will use to store the shimDisconnect data when you call the connect function

if the connector is not passed through the createConfig function, when calling connect its storage will be empty, so it won’t save this config on localStorage.

Comparing the behavior of the latest @wagmi/core release prior to 1.x with 1.x

I’m having the same issue in a Blitz.js project; on version 0.12.12 after our users connected there wallet the connection info would be retained if they left/came back, after upgrading wagmi to 1.0.2 after our users connect their wallet, the info is lost by just refreshing the page.

A workaround the OP found (and posted in #2439 comment here) was creating a Local Storage key/val that the old wagmi version created which is no longer created in 1.x:

localStorage.setItem('wagmi.injected.shimDisconnect', 'true')

I looked into ways to not need to manually create this by adding the shimDisconnect option to the InjectedConnector, but setting that to true or false did nothing to fix this.

@ombayoeco11 I had the same results as @skplunkerin – setting shimDisconnect to true (or false) has no observable impact on the autoConnect behavior.

I checked localStorage values with shimDisconnect set explicitly – the wagmi.injected.shimDisconnect key is never set.

So it appears that:

• autoConnect depends on wagmi.injected.shimDisconnect: true (when using InjectedConnector)
• setting shimDisconnect: true on InjectedConnector does not set wagmi.injected.shimDisconnect: true

So perhaps the source of the defect is with InjectedConnector handling of shimDisconnect setting.