Widget, dapp+Safe: app says 'connect wallet' when it is connected #7777

Update 2026-10-20: not what Lido hit. Their disconnect is the ConnectorAlreadyConnectedError race fixed by #8002 (their pin, v3.24.0, predates it; see FE-451). This retry gap is still real but only reachable when the host provider fails or returns no accounts on the first request, so it's moved to Backlog as hardening.

Follow-up to FE-451 (Lido, high: "sometimes, when the ETH Widget reloads, the wallet disconnects inside the embedded CowSwap widget").

Status of the original race

• The ConnectorAlreadyConnectedError race from Lido's gist was fixed in fix(wallet): swallow ConnectorAlreadyConnectedError in widget dapp-mode connect race (first shipped in v3.26.0).
• But stake.lido.fi loads the widget from https://cow-ipfs.lido.fi (cowswapWidgetBaseUrl in their /runtime/window-env.js), which serves v3.24.0. They don't have the fix.
• On v3.24.0 the error does show up, but the widget still ends up connected. Corrected 2026-10-20: with Lido's mount pattern (no provider → provider a few ms later), their v3.24.0 pin ended disconnected in 12 of 33 automated attempts; prod v3.31.1 in 0 of 11. Details in FE-451.

Remaining gap

If the host provider's first eth_accounts / eth_requestAccounts fails or comes back empty, and no accountsChanged follows, the widget stays disconnected for good.

• WidgetStandaloneModeUpdater (libs/wallet/src/updaters/WidgetStandaloneMode.updater.tsx) connects exactly once per isDappMode change and only logs on failure. wagmi's reconnect gives up too.
• Reproduced on v3.24.0 and on prod: the host wallet was ready at ~4.6s, and the widget never asked again (2 requests in total). A later accountsChanged does recover it.

Lido's provider makes this reachable:

• its synthetic connect event fires via setTimeout(0) when our bridge subscribes. That happens in createCowSwapWidget, before the iframe has loaded, so the event is lost;
• accountsChanged only fires on a wagmi change;
• their request wrapper uses retryCount: 0.

Fix idea

• In dapp mode, retry the widget connector with a bounded backoff when connect fails or returns no accounts.
• Have IframeRpcProviderBridge re-send the current accounts/chainId once the iframe posts ACTIVATE / READY, so events emitted before load aren't lost.
• Treat a connect with zero accounts as not connected (see the "Signer is missing account" crash issue).

For Lido

Update the cow-ipfs.lido.fi pin to current prod. Mount the widget only once the provider exists and keep it stable. Emit accountsChanged when the wallet becomes ready.

Related: GitHub #7777 (open), where dapp+Safe shows "connect wallet" while connected. A comment there notes that useIsRestoringConnection returns false in dapp mode.