You clicked "Approve" or "Connect" in your wallet, and you even saw a "Connected" message — but when you switch back to the DApp page, it still shows "Connect Wallet" or keeps spinning. Don't rush to click it again. First, check one thing: Has your DApp page been refreshed?
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
In about 80% of cases, the problem is not that the connection itself failed. Instead, after the connection succeeded, the browser did not receive the "connection successful" signal from the wallet, or it received the signal but the page did not update its state in time. Follow the three steps below and you should be able to fix it.
Step 1: Hard Refresh the DApp Page (Most Effective)
After the wallet confirms the connection, most DApps need to actively query the WalletConnect session state once before the UI can update. If the page does not trigger this query automatically, it gets stuck in the "not connected" state.
What to do:
Click the refresh button in the browser address bar (or press F5 / Cmd+R). But a hard refresh works even better — press Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac to clear the current page cache and reload.
If you are using a mobile browser, switch to the background and then switch back to let the page reactivate.
How to know it worked: After refreshing, your wallet address (a string starting with 0x) appears in the top right corner or middle area of the page, instead of a "Connect Wallet" button.
Some DApps use the WalletConnect protocol, but the backend does not correctly configure the chain ID callback. For example, you switched to Polygon in your wallet, but the DApp only recognizes Ethereum Mainnet by default. The handshake information does not match, so the connection state just hangs there. Refreshing the page directly makes the DApp request the current chain information from the wallet again, which often fixes the mismatch.
Step 2: Check the "Connected Sites" Status in Your Wallet
Still not working after refreshing? Then it is possible that the wallet did establish a session, but the DApp did not receive the correct account address. MetaMask had a known bug on some Android versions — the provider state was not ready when the wallet initialized, so the connection request was sent but the accountsChanged event never fired, and the DApp never received your address.
What to do:
Open your wallet app and find the "Connected Sites" or "WalletConnect" list (Trust Wallet and MetaMask both have this in settings).
Check whether the current DApp name is in the list. If it is, that means the session was indeed established.
Delete this session, go back to the DApp page, and click "Connect Wallet" again to redo the process. This time, after the connection succeeds, first switch back to the wallet to confirm you clicked "Approve" on the popup, then switch back to the DApp and refresh.
How to know it worked: The DApp entry has been successfully removed from the "Connected Sites" list in your wallet, and after reconnecting, the DApp page shows your address.
Step 3: Make Sure the Wallet and DApp Are on the Same Chain
This is another common trap. You approved the connection request in your wallet, but the DApp requires chain A while your wallet is on chain B. The connection handshake may partially succeed, but after the DApp receives your address and finds the chain does not match, it directly marks the connection state as "invalid."
What to do:
Look at the network name at the top of your wallet (such as Ethereum Mainnet / Polygon / BSC).
Look at the bottom right corner or top of the DApp page for a chain name or icon (usually something like "Network: Polygon").
If they do not match, switch to the network required by the DApp in your wallet.
How to know it worked: The network name in your wallet exactly matches the network required by the DApp. Refresh the DApp page and the status should update to connected.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
If None of the Above Works: Check Whether the Wallet or RPC Provider Is Down
Sometimes it is not your operation that is the problem. Some wallets have experienced multi-network connection outages where the user-side wallet was fine, but the underlying RPC routing was down, making it impossible for the DApp to connect no matter what.
What to do:
Go to the wallet's official Twitter/X or status page to see if there is a service interruption announcement.
If you are using MetaMask, try changing the default RPC provider in wallet settings (for example, switch from Infura to Alchemy or a public RPC).
How to know it worked: The official announcement confirms the service has been restored, or the connection succeeds after changing the RPC.
Verification method: After completing any of the steps above, the DApp page should show your wallet address (usually displayed as 0x1234...5678), and the previously grayed-out transaction button should become clickable. If it still does not work, wait 30 seconds to 1 minute and refresh again — the WalletConnect relay server sometimes has delays.
