MetaMask / MetaMask/metamask-mobile
[Bug]: Money account: adding funds with Ledger displays fee for no fee tokens, instead of Paid by MetaMask message
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### Describe the bug
When adding funds to Money account using Ledger account and selecting a token with `No fee`, then the transaction confirmation displays transaction fees.
This does not happen when using a regular account, where `Paid by MetaMask` message is displayed when selecting a token with `No fee`
### Expected behavior
Paid by MetaMask message do be displayed instead of Transaction fees when adding funds to Money account using Ledger wallet and selecting a token with No fee
### Screenshots/Recordings
https://github.com/user-attachments/assets/d2ec25da-24c0-49b6-a12d-dac25ec0d625
### Steps to reproduce
1. Add Ledger account
2. Go to Money
3. Click Add
4. Click Convert crypto
5. Select a token with No fee
6. Notice transaction fees are displayed
7. Repeat steps 2-5 for regular account
8. Notice Paid by MetaMask is displayed
### Error messages or log output
```shell
```
### Where was this bug found?
Internal release testing
### Version
8.11.0
### Build number
6848
### Build type
None
### Device
Pixel 6 Pro
### Operating system
Android
### Additional context
_No response_
### Severity
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Android flow in the issue: add a Ledger account, open Money, choose Add > Convert crypto, and select a no-fee token. Trace the transaction confirmation fee display for Ledger versus regular accounts; done means Ledger shows “Paid by MetaMask” for no-fee tokens while the regular-account behavior remains unchanged.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100