metamask-extension
metamask-extension copied to clipboard
[Bug]: Certain chains icons are not displayed in the Send flow
Describe the bug
BNB Chain and Linea Mainnet icons are not displayed in the Send flow.
Expected behavior
Network icons are properly displayed.
Screenshots/Recordings
Steps to reproduce
- Switch to BNB Chain / Linea Mainnet
- Start Send transaction
- Notice that BNB / Linea network icon is not displayed in the Send flow
Error messages or log output
No response
Version
latest build
Build type
None
Browser
Chrome, Firefox
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
Seeing this in develop as well – downgrading from a blocker
Latest build Slack discussion link.
Chrome - Linea mainnet and BNB Chain icons displayed correctly:
Is this within the scope of Swap+Send? It seems like a general/confirmations bug
Icons for BNB Chain and Linea Mainnet not disaplyed, tested on the latest send+swap build and develop
:
Looks like the network icons are still missing, but the tokens are correctly showing or at least displaying an icon other than ?
NVM it seem the token badges were resolved in https://github.com/MetaMask/metamask-extension/pull/25470
Closed by https://github.com/MetaMask/metamask-extension/pull/25470
Closing in lieu of https://github.com/MetaMask/metamask-extension/issues/25447
https://github.com/MetaMask/metamask-extension/pull/25518
This bug is present in v12.0.0 beta:
@sleepytanya Is the problem still present on the Send screen? Or only now on the confirmation screen?
@danjm It affects only Confirmation screen.
I think this PR https://github.com/MetaMask/metamask-extension/pull/25518 might fix it, but was not cherry picked to v12.0. That being said, it's not a regression (it's also present on v11.16.4) so shouldn't be considered a release blocker.
Reverting labels as discussed in release sync as the original issue was slightly different than the latest and was cherry picked to the release.
Closing as the original issue has been fixed to facilitate v12.0 bug triage. We can open a separate one for the confirmation specific issue.