A failed return from a mobile wallet can leave the swap website waiting even after you signed. The app handoff and blockchain execution are separate events, so inspect the wallet’s activity before pressing Swap again.
Find the last action
Open the wallet directly. Determine whether it recorded an approval, swap transaction or offchain signature. If there is a hash, inspect it on the correct network. If you rejected the prompt or never confirmed, the original browser session may simply be waiting for a response.
MetaMask’s mobile connection guidance identifies the account and network permissions used for an application session. Confirm those values before reconnecting a stale tab.
Re-establish the session carefully
Reopen the genuine application in its documented supported browser or connection flow. Avoid several simultaneous tabs connected to the same wallet while diagnosing the problem. Refresh the quote if no transaction was submitted.
If approval confirmed, a new session may still detect its allowance. If the swap confirmed, verify output rather than repeating the trade. If a transaction remains pending, use its existing hash to track it.
For support, include mobile operating system, wallet version, browser, connection method and whether signing occurred. A screen recording should hide balances or identifiers you do not want public and must never show a recovery phrase. Handoff failures do not require a “wallet validation” website or secret re-entry.
Sources & verification (2)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- How to connect to a dapp
Account and network permissions are part of the dapp connection.
https://support.metamask.io/more-web3/dapps/connecting-to-a-dapp - Transactions | ethereum.org
Signed transaction fields, sequential account nonce and lifecycle.
https://ethereum.org/developers/docs/transactions/