Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Send flow is broken on ETH Mainnet after NFTs are downloaded, getting error "Fiat conversions are not available...", "Balance: undefined" on Amount screen #12972

Closed
chrisleewilcox opened this issue Jan 14, 2025 · 1 comment
Labels
release-blocker This bug is blocking the next release Sev1-high An issue that may have caused fund loss or access to wallet in the past & may still be ongoing team-assets type-bug Something isn't working

Comments

@chrisleewilcox
Copy link
Contributor

chrisleewilcox commented Jan 14, 2025

Describe the bug

Wallet accounts with NFTs on ETH Mainnet will have the send flow broken for those accounts after NFTs are first detected and downloaded.

This issue currently exist in prod. Haven't found a workaround. Once user get's this then they are stuck with it forever. Restarting app, reimporting account, etc.... doesn't resolve issue.

Expected behavior

Send flow should not break if NFTs are download.

Screenshots/Recordings

Screen.Recording.2025-01-13.at.6.13.33.PM.mov

Steps to reproduce

GIVEN I am on Wallet view
AND I just imported an account
AND imported account owns NFT's on Eth Mainnet
AND imported account NFTs have not been detected yet
AND selected network is Eth Mainnet
WHEN I view NFTs on Wallet view
AND NFTs are imported successfully
THEN Send flow should not break for any account (FAILED: not able to send assets from imported account, errors on Amount screen)

Error messages or log output

Detection stage

In production (default)

Version

7.37.1

Build type

None

Device

Any

Operating system

iOS, Android

Additional context

No response

Severity

No response

@chrisleewilcox chrisleewilcox added the type-bug Something isn't working label Jan 14, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Jan 14, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Jan 14, 2025
@metamaskbot metamaskbot added the regression-prod-7.37.1 Regression bug that was found in production in release 7.37.1 label Jan 14, 2025
@chrisleewilcox chrisleewilcox added release-blocker This bug is blocking the next release Sev1-high An issue that may have caused fund loss or access to wallet in the past & may still be ongoing team-assets and removed regression-prod-7.37.1 Regression bug that was found in production in release 7.37.1 labels Jan 14, 2025
@chrisleewilcox
Copy link
Contributor Author

closing as this was already reported #12317

@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by team Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker This bug is blocking the next release Sev1-high An issue that may have caused fund loss or access to wallet in the past & may still be ongoing team-assets type-bug Something isn't working
Projects
Archived in project
Status: Fixed
Development

No branches or pull requests

2 participants