What happens to my swap if the mobile app closes or crashes midway

07 September 2026

It depends entirely on whether the swap had been broadcast to the blockchain before the crash. If the transaction was already sent, it will complete regardless of what happens to your app. If it was not yet sent, nothing happens - the swap never started.

The critical distinction: before broadcast vs. after broadcast

A mobile swap involves several steps. You enter the amounts, confirm the rates, and then the app prepares a transaction. Only the final step - broadcasting that transaction to the network - actually commits your funds.

If the app crashes before broadcast: No transaction exists on the blockchain. Your tokens remain untouched in your wallet. You simply open the app again, or use a different wallet interface, and start over. There is nothing to recover because nothing was ever at risk.

If the app crashes after broadcast: The transaction is already on the network. Miners or validators will process it as usual. Your swap will settle, and the resulting tokens will arrive at your destination address, even if you never open the app again. You can confirm the status by looking up your wallet address on a blockchain explorer from any device.

The in-between: the app closes during the broadcast

This is the only genuinely ambiguous scenario. If the app crashes while the broadcast is in progress, one of two things is true: either the network received the transaction, or it did not. Most wallets will try to resend on relaunch, but not all handle retries reliably.

If you reopen the app and your balance is unchanged, inspect your wallet address on a block explorer. If the outgoing transaction appears there, the swap is in progress. If it does not, no funds moved and you can safely restart.

What can go wrong in a mobile wallet swap

The hub page "Mobile wallet swap safety mistakes to avoid" covers full list of pitfalls, but the crash scenario highlights one specific mobile risk: reliance on a single connection. A desktop computer plugged into a stable network seldom drops a transaction mid-broadcast. A phone moving between WiFi and cellular, or simply running out of battery, does that routinely.

Two practical things reduce your exposure:

Confirm the transaction ID before closing the app. Most wallets show a transaction hash (TXID) immediately after sending. Note it down or screenshot it. With that hash, you can verify completion on any device, anytime.

Do not rely on the app's history alone. If the app crashes and you later reinstall or switch phones, the local transaction log may be gone. The blockchain record - accessed via a block explorer - is the only permanent truth.

The clipboard and QR code risks are separate

Sibling pages cover "Why is copying a wallet address on a phone riskier than on a desktop," "How does clipboard malware steal crypto during a mobile swap," and "What should I check when scanning a QR code for a swap deposit address." Those are genuine threats. The crash scenario is not a theft risk; it is a confusion risk. You lose nothing but time and confidence.

The practical test

If your app closes mid-swap, do this:

1. Open a block explorer on any device.
2. Paste your wallet address.
3. Look for a recent outgoing transaction matching the swap amount.
4. If you see it, wait. The swap completes on the network, not in your app.
5. If you see nothing, the swap never happened. You can retry safely.

No mobile swap ever depended on your phone staying alive after the network accepted the transaction. The network does not know or care about your app. Once the signature is out there, the swap runs on its own.

Back to trezor