fix(wallet): preserve explicit URL chain across refresh on reconnect - #7910

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== locate file =="
fd -a 'useSetupTradeState\.ts$' . || true

echo "== target file outline =="
ast-grep outline apps/cowswap-frontend/src/modules/trade/hooks/setupTradeState/useSetupTradeState.ts --view expanded || true

echo "== target file relevant sections =="
cat -n apps/cowswap-frontend/src/modules/trade/hooks/setupTradeState/useSetupTradeState.ts | sed -n '1,180p'

echo "== connectionStatus references in repo =="
rg -n "connectionStatus|wasConnectionRestoredRef|useConnection" apps/cowswap-frontend/src/modules/trade src -S || true

Repository: cowprotocol/cowswap

Length of output: 11166

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== locate dependency versions =="
fd -a '(^package\.json$|^yarn\.lock$|^package-lock\.json$|^pnpm-lock\.yaml$)' . | sed 's#^\./##' | head -100

echo "== wagmi versions =="
rg -n '"wagmi"|"`@wagmi/core`"|"`@wagmi/connectors`"' apps/cowswap-frontend/package.json package.json yarn.lock pnpm-lock.yaml package-lock.json 2>/dev/null || true

echo "== package files =="
for f in apps/cowswap-frontend/package.json package.json; do
  if [ -f "$f" ]; then
    echo "--- $f ---"
    cat "$f" | jq '.dependencies.wagmi, .dependencies["`@wagmi/core`"], .dependencies["`@wagmi/connectors`"], .devDependencies.wagmi, .devDependencies["`@wagmi/core`"], .devDependencies["`@wagmi/connectors`"]' 2>/dev/null || cat "$f"
  fi
done

echo "== deterministic state machine based on source behavior =="
python3 - <<'PY'
from pathlib import Path
p = Path("apps/cowswap-frontend/src/modules/trade/hooks/setupTradeState/useSetupTradeState.ts")
text = p.read_text()
checks = {
    "latch_declared": "useRef(false)" in text and "wasConnectionRestoredRef" in text,
    "latch_set_reconnecting": "connectionStatus === 'reconnecting'" in text and "wasConnectionRestoredRef.current = true" in text,
    "latch_never_reset_in_setter": "wasConnectionRestoredRef.current = false" not in text,
    "latch_used_in_chain_decision": "wasConnectionRestoredRef.current" in text,
    "latch_effect_deps_connectionStatus": "[connectionStatus]" in text,
}
for k, v in checks.items():
    print(f"{k}: {v}")
PY

Repository: cowprotocol/cowswap

Length of output: 2388

🌐 Web query:

wagmi 3.6.9 useConnection status disconnected reconnecting failed connect

💡 Result:

In Wagmi v3.6.9, the useConnection hook provides the current connection state of your application [1][2]. The status property of this hook returns one of four string values representing the connection lifecycle [1]: 'connecting': The application is currently attempting to establish a connection. 'reconnecting': The application is attempting to re-establish a connection to one or more previously connected connectors (often triggered automatically on page load). 'connected': At least one connector is currently active and connected [1]. 'disconnected': There is no active connection to any connector [1]. If you are observing a state that transitions between these, it is typical behavior for Wagmi to manage its connection state automatically [3]. For example, if the status shows as 'reconnecting', Wagmi is likely performing an auto-connection process; if it ends in 'disconnected', the attempt to restore the previous session has failed [1]. To manage these states in your UI, you can use the boolean flags derived from the status, such as isConnecting, isReconnecting, isConnected, and isDisconnected [1]. You can also use the useConnectionEffect hook if you need to trigger specific actions (like logging or UI alerts) specifically when a connection is established or lost [4]. If you are facing persistent issues where the status remains 'disconnected' after an attempted connection, ensure that your Wagmi Config is correctly initialized and that your connectors are configured to support auto-connection if desired [3].

Citations:

• 1: https://wagmi.sh/react/api/hooks/useConnection
• 2: https://cdn.jsdelivr.net/npm/[email protected]/dist/types/hooks/useConnection.d.ts
• 3: https://wagmi.sh/react/guides/faq
• 4: https://app.unpkg.com/[email protected]/files/src/hooks/useConnectionEffect.ts

🌐 Web query:

site:wagmi.sh/reference/hooks/useConnection status disconnected reconnecting wagmi 3

💡 Result:

The URL appears invalid: https://wagmi.sh/reference/hooks/useConnection returns 404. In current Wagmi docs, connection state is exposed through useAccount, whose status can be:

'connecting' | 'reconnecting' | 'connected' | 'disconnected'

Example:

const { status, isConnected } = useAccount()

if (status === 'reconnecting') {
  // Restoring a previously persisted wallet connection
}

if (status === 'disconnected') {
  // No wallet is connected
}

Wagmi’s current documentation site lists React hooks but does not appear to provide a useConnection hook reference. [1][2]

🌐 Web query:

github wagmi isAutoReconnecting reconnecting status source

💡 Result:

In Wagmi, the isReconnecting flag and the reconnecting status are used to track whether a wallet is in the process of automatically reconnecting to a previously used connector, typically upon application load [1][2][3]. Core Details: - Status: The account status is a state that can be 'connecting', 'reconnecting', 'connected', or 'disconnected' [1][4]. - isReconnecting: This boolean flag is true when the application is attempting to restore a previous session (e.g., via auto-connect) [1][2][3]. - isConnected vs. Reconnecting: A known point of discussion is that while status is 'reconnecting', isConnected may return false or a boolean depending on the version and specific internal state, as the connection is not yet fully established [4]. - Reconnect Action: In modern versions of Wagmi (e.g., v2+), there is an explicit reconnect action provided by @wagmi/core that can be used to manually trigger reconnection to specific connectors [5]. The behavior of these flags is managed by the Wagmi config [6][7]. In older versions, an autoConnect property was used in the configuration [7], whereas newer versions may handle this through different lifecycle mechanisms or the reconnect action [5]. If you encounter an application getting stuck in a 'reconnecting' state, it is often related to component re-renders or hydration issues where the connection effect is not being triggered or cleaned up correctly [8].

Citations:

• 1: https://1.x.wagmi.sh/react/hooks/useAccount
• 2: https://0.9.x.wagmi.sh/react/hooks/useAccount
• 3: https://0.10.x.wagmi.sh/react/hooks/useAccount
• 4: [BUG]: isConnected is incorrect wevm/wagmi#4050
• 5: https://wagmi.sh/core/api/actions/reconnect
• 6: https://1.x.wagmi.sh/core/config
• 7: https://0.9.x.wagmi.sh/react/config
• 8: wagmi stays in the reconnecting: true state during the hot-reload wevm/wagmi#3490

🌐 Web query:

github wagmi v3 useConnection implementation useAccount isReconnecting

💡 Result:

In Wagmi v3, the hook previously known as useAccount has been renamed to useConnection [1]. This change reflects a more accurate representation of how Wagmi manages connections between applications and Ethereum providers [1]. When using useConnection to check for reconnection status, you can access the isReconnecting boolean property, which is derived from the current connection status [2]. The status property returned by useConnection can be one of four values [2]: - 'connecting': Attempting to establish a connection. - 'reconnecting': Attempting to re-establish a connection to one or more connectors. - 'connected': At least one connector is connected. - 'disconnected': No connection to any connector. The isReconnecting flag is a boolean that provides a direct way to check if the application is currently in the 'reconnecting' state [2]. This is typically used to handle UI states while the application attempts to re-establish a session, such as after a page refresh or when auto-connect is active [2]. Example usage: import { useConnection } from 'wagmi' function ConnectionStatus { const { isReconnecting, status } = useConnection if (isReconnecting) { return

Citations:

• 1: https://wagmi.sh/react/guides/migrate-from-v2-to-v3
• 2: https://wagmi.sh/react/api/hooks/useConnection

🌐 Web query:

github wevm wagmi v3 useConnection hook source isAutoReconnecting connecting reconnecting

💡 Result:

In Wagmi v3, the useAccount hook from previous versions has been renamed to useConnection to better reflect the library's connection model [1][2]. The useConnection hook returns an object that includes several boolean flags and a status property, which are derived from the current connection state [3]. Key properties returned by useConnection: - status: This property can be one of four values: 'connecting', 'reconnecting', 'connected', or 'disconnected' [3]. - 'connecting': The application is attempting to establish a connection. - 'reconnecting': The application is attempting to re-establish a connection to one or more connectors. - 'connected': At least one connector is active. - 'disconnected': No connections are active. - Derived booleans: Based on the status, the hook also provides boolean properties such as isConnecting, isReconnecting, isConnected, and isDisconnected [3]. Regarding isAutoReconnecting: It is important to note that the useConnection hook does not explicitly provide an isAutoReconnecting property [3]. The reconnection process is internally handled by Wagmi, and when the system is in the process of re-establishing previous connections (often triggered by auto-connect logic), the status will be 'reconnecting', and the isReconnecting boolean will be true [3]. Source Implementation: The useConnection hook is implemented using useSyncExternalStoreWithTracked to ensure it stays in sync with the underlying Wagmi configuration [4]. It utilizes the watchConnection function from @wagmi/core to monitor connection changes and retrieve the current state via getConnection [4]. Technical Context: Wagmi v3 simplifies the API to better align with TanStack Query patterns, and developers are encouraged to use the returned status to narrow the return type [3][2]. For instance, when the status is 'connected', properties like address are guaranteed to be defined [3]. If you are encountering issues where the application appears to hang in a specific state (like isReconnecting), this may be related to hydration or mount cycles, which have been topics of discussion in the project's issue tracker [5][6].

Citations:

• 1: https://wagmi.sh/react/guides/migrate-from-v2-to-v3
• 2: https://www.ignaciopastorsanchez.com/blog/how-to-read-from-a-smart-contract-using-wagmi-v3
• 3: https://wagmi.sh/react/api/hooks/useConnection
• 4: https://app.unpkg.com/[email protected]/files/src/hooks/useConnection.ts
• 5: wagmi stays in the reconnecting: true state during the hot-reload wevm/wagmi#3490
• 6: fix: allow excessive hydration to fix hanging isReconnecting state wevm/wagmi#3492

🌐 Web query:

github wevm wagmi src hooks useConnection

💡 Result:

In the current version of the Wagmi library (wagmi), the useConnection hook is a provided React hook used to retrieve the current connection status and details [1]. It allows you to access information about the connected account and chain within your React components [1]. Key details about useConnection: - Import: It is imported directly from the wagmi package: import { useConnection } from 'wagmi' [1]. - Functionality: It provides the connected address, addresses, chain, connector, and status (e.g., connecting, connected, disconnected) [1]. - Derived State: It also provides boolean flags like isConnecting, isReconnecting, isConnected, and isDisconnected, which are derived from the connection status [1]. Related hooks: - useConnect: Used specifically for initiating a connection to a wallet/connector [2][3]. - useConnectionEffect: A hook for performing side effects (like callbacks) when connection status changes (e.g., onConnect, onDisconnect) [4]. You can find the official documentation and API reference for this hook on the Wagmi website [1].

Citations:

• 1: https://wagmi.sh/react/api/hooks/useConnection
• 2: https://wagmi.sh/react/api/hooks/useConnect
• 3: https://1.x.wagmi.sh/react/hooks/useConnect
• 4: https://app.unpkg.com/[email protected]/files/src/hooks/useConnectionEffect.ts

🌐 Web query:

"hasAnyConnector" "isAutoReconnecting" useConnection wagmi

💡 Result:

In the context of Wagmi, the terms you mentioned relate to account connection and auto-reconnection state, though their availability depends on the specific version of the library you are using [1][2]. 1. isReconnecting: This is a standard property available in the useAccount hook (in Wagmi v1.x and earlier) that indicates whether the application is currently attempting to automatically reconnect to the last used connector [1]. It is part of the account status object [1]. 2. useConnection: This is a hook introduced in newer versions of Wagmi (e.g., v3+) as a replacement for useAccount [2]. It provides access to account information, such as the connected address, connection status, and chain ID [2]. 3. hasAnyConnector / isAutoReconnecting: There are no standard, public-facing hooks or properties by these exact names in the official Wagmi documentation [3][1][4][5]. For auto-reconnection behavior: - In older versions (v0.x/v1.x), auto-reconnection was configured via the autoConnect property in createConfig [3][6]. - If you are experiencing issues with reconnection, ensure your connectors are correctly registered within the createConfig function, as this allows Wagmi to properly manage their storage for session persistence [7]. If you are transitioning to Wagmi v3, note that the API has changed significantly, such as using useConnection for account state and using separate hooks like useConnectors for managing connector lists [2]. Always refer to the specific documentation for your installed version [2].

Citations:

• 1: https://1.x.wagmi.sh/react/hooks/useAccount
• 2: https://docs.metamask.io/metamask-connect/evm/quickstart/wagmi/
• 3: https://1.x.wagmi.sh/core/config
• 4: https://1.x.wagmi.sh/react/hooks/useConnect
• 5: https://1.x.wagmi.sh/examples/connect-wallet
• 6: https://0.9.x.wagmi.sh/react/config
• 7: bug: autoConnect fails to reconnect wevm/wagmi#2511

🌐 Web query:

"github.com/wevm/wagmi" "src/hooks" "useConnection.ts" "isAutoReconnecting"

💡 Result:

In modern versions of wagmi (v2+), there is no property named isAutoReconnecting on the useConnection hook or related connection state [1][2]. The wagmi library manages reconnection state via the status property, which can be one of 'connecting', 'reconnecting', 'connected', or 'disconnected' [1]. The useConnection hook (and similar hooks like useAccount) provide boolean flags derived from this status, specifically isReconnecting (for when the library is attempting to re-establish a connection) [1][3]. Key technical details regarding connection state: - The isReconnecting flag is used to indicate that the library is currently attempting to re-establish a connection to one or more previously used connectors [1]. - In earlier versions of wagmi (v1.x), the autoConnect configuration was used to enable automatic reconnection [4]. In current versions, this is handled automatically by the wagmi configuration on mount [5]. - Issues related to the "hanging" of the isReconnecting state during development (e.g., during hot-module replacement) have been documented in the wagmi repository, where the state may fail to transition correctly if the component lifecycle behavior during re-renders is not handled as expected [5][6]. If you are looking for a boolean to check if the library is in the process of reconnecting, you should use the isReconnecting flag provided by useConnection or useAccount [1][3].

Citations:

• 1: https://wagmi.sh/react/api/hooks/useConnection
• 2: https://cdn.jsdelivr.net/npm/[email protected]/dist/types/hooks/useConnection.d.ts
• 3: https://1.x.wagmi.sh/react/hooks/useAccount
• 4: https://1.x.wagmi.sh/core/config
• 5: wagmi stays in the reconnecting: true state during the hot-reload wevm/wagmi#3490
• 6: fix: allow excessive hydration to fix hanging isReconnecting state wevm/wagmi#3492