fix: only reconnect accounts for active chain during rehydration

[jakehobbs]

Bug when switching chains after refreshing page

Explanation

• When the page is refreshed, the store is rehydrated using the cookie data.
• The hydrate function calls hydrateAccountState, which reads all existing accounts from the store and sets them to "RECONNECTING" on all chains.
• The hydrate function then calls the reconnect function, which calls createAccount for each account. But this only happens on the active chain, so any other chain's accounts will get stuck in the "RECONNECTING" state but never actually reconnect.

Solutions

• The easiest solution is to not set accounts to "RECONNECTING" if they are not on the active chain during hydration. We can just set them to "DISCONNECTED", then they will naturally reconnect if they are attempted to be used again.
• An alternative solution would be to alter the createAccount function to accept an option chain param instead of only being able to reconnect accounts on the active chain.

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR focuses on enhancing the account state management by introducing an activeChainId that determines if the current chain is active, affecting the reconnection logic for various account types.

Detailed summary

• Added activeChainId to track the current active chain.
• Introduced isActiveChain to check if the current chain matches activeChainId.
• Updated the reconnection logic for LightAccount, MultiOwnerModularAccount, MultiOwnerLightAccount, and ModularAccountV2 to consider shouldReconnect based on the active chain.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 12, 2025 6:17pm
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 12, 2025 6:17pm

[graphite-app]

How to use the Graphite Merge Queue

Add the label graphite-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[adamegyed]

Good job digging through the stack to find this!

Do you know if setChain from useChain will automatically start the re-connect process? https://accountkit.alchemy.com/react/multi-chain-apps#change-chains

[jakehobbs]

Good job digging through the stack to find this!

Do you know if setChain from useChain will automatically start the re-connect process? https://accountkit.alchemy.com/react/multi-chain-apps#change-chains

it does not. the only place reconnect is called is during rehydration.