Description

The advanced chart time axis was always displaying in UTC regardless of the user's locale.

Root cause: The timezone property was missing from the TradingView.widget constructor. When omitted, falls back to the symbol's resolveSymbol timezone — hardcoded to Etc/UTC for our crypto data.

Fix: Detect the user's timezone via Intl.DateTimeFormat().resolvedOptions().timeZone and pass it to the widget constructor. The value is validated against TradingView's supported timezone list with a fallback to Etc/UTC.

Note: the timezone: 'Etc/UTC' in resolveSymbol is unchanged, it declares data alignment, which is separate from the display timezone.

Changelog

CHANGELOG entry: Fixed advanced chart displaying timestamps in UTC instead of the user's local timezone

Related issues

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

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.