Description

Fixes a crash that occurred when viewing token details on custom or unsupported networks (e.g., Fantom, Linea Sepolia, custom EVM chains).

Issue

When users navigated to token details on networks not supported by the Swaps/Bridge formatAddressToAssetId, the app would crash with:

Error: No XChain Swaps native asset found for chainId: eip155:59141

Reproduction Steps:

1. Navigate to a custom network (e.g., Fantom with chainId 0xfa)
2. Select any token on that network
3. App crashes when trying to display token details

Solution

Added a try-catch wrapper around the formatAddressToAssetId call in Price.advanced.tsx. When the function throws an error for unsupported chains:

Changelog

CHANGELOG entry: Fix navigation error on token details page when coming from custom network flow

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

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.