fix: Toast component theme reactivity in production builds cp-7.59.0

[georgewrmarshall]

Description

Fixed Toast component theme not updating when switching between light and dark mode in production builds (TestFlight). The issue only affected production builds while working correctly in development/simulator.

Root Cause:

The Toast component had an empty dependency array [] in its useMemo hook (line 69), which cached the initial theme styles and never updated when the theme changed. This was a remnant from when Toast used inverse/hardcoded theming.

Solution:

Updated the useMemo dependency array to properly track [styles.base, animatedStyle], ensuring the component re-renders with correct theme colors when theme changes occur.

Changelog

CHANGELOG entry: Fixed Toast component not updating theme colors when switching between light and dark mode

Related issues

Fixes: Theme change issue in Toast component

Manual testing steps

Feature: Toast theme updates correctly

  Scenario: User switches device theme while Toast is visible
    Given the app is running with a visible Toast notification
    
    When user switches from light mode to dark mode (or vice versa) in device settings
    Then the Toast should update to match the new theme colors immediately
    
  Scenario: Toast appears with correct theme in production build
    Given the app is running in a TestFlight production build
    And user has dark mode enabled
    
    When a Toast notification appears
    Then the Toast displays with correct dark theme colors (not stuck in light theme)

Screenshots/Recordings

Before

Toast remained in previous theme colors when device theme was changed in production builds.

before.MP4

After

Toast correctly updates to match current theme in both development and production builds.

after.MP4

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.

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.

---

Note

Update Toast baseStyle useMemo to depend on styles.base and animatedStyle (and simplify its type) so styling updates correctly.

^{Written by Cursor Bugbot for commit 1a4dca6. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[georgewrmarshall]

The empty dependency array [] cached the initial theme styles and never updated when the theme changed. This was a remnant from when Toast used inverse/hardcoded theming.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud