MetaMask / MetaMask/metamask-mobile
[Bug]: Send NFT - Confirmation screen is broken if we try to send an NFT with NFT details disabled from settings
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
**Describe the bug**
Confirmation screen is broken if we try to send an NFT with NFT details disabled from settings.
The Confirmation page doesn't display the recipient, fee, network etc. as usual
**Expected behavior**
Confirmation screen should be the same as when we have NFT details enabled, just the pic shouldn't be displayed
**Screenshots/Recordings**
https://github.com/user-attachments/assets/d2401d4d-d55c-47db-bf94-ee5985a5aafd
**Steps to reproduce**
1. Go to privacy settings
2. Disable the NFT and IPFs data
3. Start send NFT
4. Proceed to last confirmation screen --> see no network, fee, recipient etc are displayed
5. Do the same but with NFT details enabled and see how the screen is back to normal again
(if you don't have any NFT you can deploy and mint from the test dapp ERC721)
**Error messages or log output**
```shell
```
**Where was this bug found?**
Internal release testing
**Version**
8.4.0
**Build number**
6186
**Device**
Pixel 6
**Operating system**
Android
Contributor guide
Research direction
Reproduce the send-NFT flow on Android with NFT and IPFS data disabled, then compare the confirmation screen with the enabled state described in the issue. Trace the confirmation-screen entry point and its handling of disabled NFT details; done means the recipient, fee, and network are shown while only the NFT picture is omitted.
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
- 55/100