Description

This PR fixes token logo rendering for non-native assets when asset.image is empty (the issue affecting mUSD/Money integration).

The AssetLogo component now:

• computes a fallback icon URL via getAssetImageUrl when the primary image is missing,
• only attempts fallback generation for valid CAIP or strict-hex chain IDs,
• passes imageSource={{ uri: imageUri }} so undefined URI values are handled directly by AvatarToken.

It also adds unit tests to cover fallback behavior and unsupported chain-id behavior.

Changelog

CHANGELOG entry: fix: fixed token list items to use a fallback icon when token image URLs are missing

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-3156

Manual testing steps

Feature: Token list item image fallback

  Scenario: Token with missing image URL still shows an icon
    Given a token list item where asset.image is empty
    When the token list item renders
    Then AssetLogo resolves and uses a fallback image URL for valid chain IDs
    And the token icon is shown instead of an empty image

  Scenario: Unsupported chain id does not crash icon rendering
    Given a token list item where asset.image is empty and chainId is unsupported
    When the token list item renders
    Then AssetLogo does not attempt invalid fallback URL generation
    And AvatarToken renders safely when uri is undefined

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.