Skip to content

[Bug]: Upgrade from 12.15 -> 12.16 causes NFTs to disappear from custom networks #32480

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

Open
alfeng6 opened this issue May 2, 2025 · 0 comments
Assignees
Labels
needs-triage Issue needs to be triaged regression-prod-12.16 Regression bug that was found in production in release 12.16 team-assets type-bug Something isn't working

Comments

@alfeng6
Copy link

alfeng6 commented May 2, 2025

Describe the bug

Users cannot see their NFTs on custom networks after upgrading to 12.16. From early investigation, it appears to be a UI issue as their NFTs are still in state.

Expected behavior

NFTs show up after upgrading versions.

Screenshots/Recordings

No response

Steps to reproduce

  1. Open MM 12.15
  2. Upgrade to MM 12.16
  3. See that no NFTs show up on custom networks like Shape blockchain and Galactica-Reticulum

Error messages or log output

Detection stage

In production (default)

Version

12.16

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

Happening for this wallet: 0xd8c5C5aC70811aC544200A5399A0daa06C8B5bbD

And this one:
Users wallet:
0x71Bb9BD882e8cd0D118C8D9CaFC63b1C51da9C14
NFT:
0xbB8F2711bd4BC98223990267f771E97d2d9Bc167
ID: 727

Severity

No response

@alfeng6 alfeng6 added the type-bug Something isn't working label May 2, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity May 2, 2025
@github-project-automation github-project-automation bot moved this to To be triaged in Bugs by team May 2, 2025
@metamaskbot metamaskbot added regression-prod-12.16 Regression bug that was found in production in release 12.16 needs-triage Issue needs to be triaged labels May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Issue needs to be triaged regression-prod-12.16 Regression bug that was found in production in release 12.16 team-assets type-bug Something isn't working
Projects
Status: To be fixed
Status: To be triaged
Development

No branches or pull requests

4 participants