MetaMask / MetaMask/metamask-mobile

[Bug]: Failed BTC transaction shows as "Confirmed" in transaction list but "Failed" in transaction details

Open
#31,452 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-triage regression-RC-7.82.0 Sev2 ta-needs-engineer-escalation ta-triaged team-social-ai type-bug
Dominant language
TypeScript
Stars
3k
Forks
1.7k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

### Describe the bug

When a user navigates to the BTC Asset Details page, opens the Quick Buy/Sell bottom sheet, and a transaction fails, the **transaction list shows the transaction status as "Confirmed"**. However, when opening the transaction details, the status is correctly shown as **"Failed"**. This inconsistency misleads the user into thinking the transaction succeeded.

### Expected behavior

The transaction status should be consistent across both the transaction list and the transaction detail view. A failed transaction should be displayed as "Failed" in all places.

### Screenshots/Recordings

_Reporter to attach screenshot/recording if available._

### Steps to reproduce

1. Navigate to the Asset Details page for **BTC**
2. Tap the **Quick Buy** button
3. Complete the flow so that a transaction is submitted and **fails**
4. Navigate to the **transaction list**
5. Observe the failed transaction is displayed as **"Confirmed"**
6. Tap on the transaction to open the **transaction details**
7. Observe the status now correctly shows **"Failed"**

### Error messages or log output

https://github.com/user-attachments/assets/72165fb5-1a78-4885-8f4a-650638454498

### Where was this bug found?

Internal release testing

### Version

7.82.0

### Build number

5382

### Build type

_No response_

### Device

iPhone

### Operating system

iOS

### Additional context

- Token: BTC
- The status discrepancy between transaction list ("Confirmed") and transaction details ("Failed") could cause users to believe funds were successfully moved when they were not.
- Team: Social

### Severity

_To be filled by internal support / PM_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the flow from the BTC Asset Details page through the Quick Buy/Sell bottom sheet, then compare the transaction list and transaction details status handling. Trace how a failed transaction is mapped for each view; done means the list and details both display "Failed" for the same failed transaction.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
frontend, mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.