Connect wallet doesn't work if stored chain id doesn't exist

[usame-algan]

Bug description

To initialize onboard we need to pass a chainId in order to decide which wallets to enable. This chainId comes from useChainId which in turn gets the chainId from different sources in the following order:

• From the url e.g. ?chain=1
• From local storage under session.lastChainId depending on the safe that was last opened
• From the connected wallet -> This is undefined because a wallet can only be connected once onboard is ready
• From the default chain id which is either mainnet (1) or sepolia on dev environments (11155111)

However there are issues in case the user has a chainId stored under session.lastChainId that doesn't exist anymore in the chains config. This can happen if:

• Switching between staging and prod config (only an issue for users working in both environments)
• Turning off a network (temporarily)

Environment

• Browser: Any
• Wallet: Any
• Chain: Any

Steps to reproduce

1. Go to app.safe.global and open a safe on a network that is not supported
2. Observe the chainId of that network is stored in local storage under session.lastChainId
3. Go to the welcome page
4. Try to connect your wallet

Expected result

Different options:

• Connect button should be disabled
• There should be an error that the wallet could not be initialized (e.g. because the network detected can't be found) and an option to "reset" the network
• ...

Obtained result

Nothing happens

[chiranjeev13]

Hey @usame-algan I m struggling to reproduce this i tried clearing my cookies aswell but connect wallet always pops up for me here is what i did ->

• Opened app.safe.global
• Connected to metamask with just zkSyncEra mainnet connected to it
• Took me to the onboard page(https://app.safe.global/welcome/accounts)
• Then i just returned back to the welcome page and disconnected metamask
• but I was still able to connect my wallet again

Am I missing something would be really helpful if you can send a screen recording to reproduce