[bug] Disconnect not persisting and reconnecting on page load

Is there an existing issue for this?

• I have searched the existing issues

Package Version

0.0.17

Current Behavior

Using a Next.js app, Im calling the disconnect function from the useAccount hook. It does disconnect but then after refreshing the page it reconnects again and the account info re-populates

Expected Behavior

I would expect to be disconnected from ym wallet so that I may be able to reconnect again with a different wallet or simply use the site in its disconnected state

Steps To Reproduce

1. Connect via InjectedConnector -> useAccount becomes populated with data and useConnect returns connected:true.
2. Press disconnect button which calls the disconnect function. -> useAccount returns empty data as expected and connected: false.
3. Refresh the page
4. usAccount becomes populated with data again and connected:true

Anything else?

No response

Edit: It seems as though if I remove autoConnect prop on the provider then it does indeed keep me disconnected however that then means on every refresh I need to reconnect. Ideally I would like connect automatically until I explicitly call disconnect

[sammdec]

Ah ok yeah that makes sense! Happy to stick what the most default behaviour is in that case

[tmm]

@sammdec MM (and other injected providers) don’t support programmatically disconnecting.

I agree it’s confusing to reconnect on page reload, but technically it’s the most accurate since the account is still connected to the browser. (wagmi does handle disconnect events coming from connector directly. For example, disconnecting in MM UI.)

That said, you could manage connection status separately in the browser, but you would need to listen and handle different connection events (i.e. disconnecting or switching account directly through MM extensions).