Description

Adds Sentry performance traces for token-overview advanced chart visibility (time from series change until skeleton clears), with separate trace types for dashboards to distinguish initial load / asset or currency changes from time-range-only updates.
Also fixes a bug in metrics consent detection during early Sentry initialization.

Changes

Advanced Chart Performance Tracing

AdvancedChart component:

• Added optional onSkeletonHidden callback that fires once when loading/layout settles and the chart is ready
• Guarded by refs to reset when series key or HTML content changes
  PriceAdvanced component:
• Starts trace() when ohlcvSeriesKey changes
• Ends trace via endTrace() when:
  • Skeleton hides (chart ready)
  • Chart error occurs
  • Trace is superseded by a newer series
  • Falls back to legacy chart
• getAdvancedChartVisibilityTraceRequest() selects appropriate TraceName and TraceOperation based on what changed:
  • Same asset + currency with only range change → TokenOverviewAdvancedChartTimeRangeVisible trace
  • Otherwise → TokenOverviewAdvancedChartInitialVisible trace
    trace.ts:
• Added new TraceName values:
  • TokenOverviewAdvancedChartInitialVisible - for initial load or asset/currency changes
  • TokenOverviewAdvancedChartTimeRangeVisible - for time range selector changes only
• Added new TraceOperation values:
  • token_overview.advanced_chart - initial load or asset/currency change
  • token_overview.advanced_chart_time_range - time range change only

Metrics Consent Fix

Problem:
The original implementation attempted to read from analytics.isEnabled() during Sentry initialization in index.js:45. However, this occurs before Engine and Redux are initialized, causing analytics.isEnabled() to incorrectly return false even for opted-in users (it checks in-memory state that doesn't exist yet).
Solution:
hasMetricsConsent() now reads directly from AnalyticsController's persisted state in FilesystemStorage (persist:AnalyticsController) before falling back to the legacy METRICS_OPT_IN storage key. This approach:

• Works before Engine/Redux initialization (FilesystemStorage is always available)
• Reads the actual persisted opt-in value from disk ({"optedIn": true/false})
• Follows the same pattern as ControllerStorage.getAllPersistedState() in persistConfig/index.ts
• Avoids dependency on deprecated METRICS_OPT_IN as the primary source
  MetaMetricsAndDataCollectionSection:
• Calls updateCachedConsent() when user toggles analytics participation
• Ensures in-memory consent cache stays synchronized with AnalyticsController state

Changelog

CHANGELOG entry: Adds tracing for advanced charts

Related issues

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

Manual testing steps

Feature: Advanced Chart Performance Tracing

  Scenario: user opens token details and chart loads successfully
    Given the user is on the home screen

    When user taps on a token to open token details
    Then a single "Starting sampled root span" log appears for "Token Overview Advanced Chart Initial Visible"
    And a single "Finishing" log appears for the same span ID
    And no duplicate "Token Overview" traces appear

  Scenario: user navigates back before chart finishes loading
    Given the user is on token details with the chart still loading (skeleton visible)

    When user quickly navigates back to the home screen
    Then a "Finishing" log appears for the "Token Overview Advanced Chart Initial Visible" span
    And the finish log appears after the navigation back (after "[UserInteraction]" log)

  Scenario: user navigates back after chart has loaded
    Given the user is on token details and the chart has fully loaded

    When user navigates back to the home screen
    Then no "Token Overview" trace logs appear during navigation back

  Scenario: user changes time range on the chart
    Given the user is on token details with the chart loaded on 1D range

    When user taps on the 1W time range selector
    Then a "Finishing" log appears for the previous "Token Overview Advanced Chart Initial Visible" span
    And a new "Starting sampled root span" log appears for "Token Overview Advanced Chart Time Range Visible"
    And a "Finishing" log appears for the new span when the chart reloads

How to verify locally:
1. Enable Sentry trace logging by filtering console output for "Tracing"
2. Navigate to a token's details screen
3. Confirm you see exactly ONE "Starting sampled root span" for
   "Token Overview Advanced Chart Initial Visible" followed by ONE
   "Finishing" log for the same span ID
4. Navigate back — confirm no additional trace start/finish for that span
5. Re-enter the token, change time range — confirm the old trace ends
   with superseded and a new "Time Range Visible" trace starts and finishes

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.