Description

1. Reason: On Activity, the Perps tab is gated by selectIsEvmNetworkSelected. After choosing Solana and then All popular networks, isEvmSelected stayed false, so Perps did not return (TMCU-672). An earlier approach called selectPopularNetwork('eip155:1') after enableAllPopularNetworks(), which fixed Perps but incorrectly forced the global EVM chain to Ethereum mainnet, so the network picker showed Ethereum instead of aggregate popular networks.

2. Solution: Keep selectAllPopularNetworks limited to NetworkEnablementController.enableAllPopularNetworks() (no implicit chain switch). Drive Activity Perps visibility with useNetworksByCustomNamespace (eip155, popular): show Perps when the Perps feature flag is on and either the user is on EVM (isEvmSelected) or all popular EVM networks are enabled—without changing the active multichain selection.

Changelog

CHANGELOG entry: Fixed the Activity Perps tab not reappearing after switching the transaction network filter back to popular networks from Solana, without forcing Ethereum as the selected chain.

Related issues

Fixes #29053
Refs: https://consensyssoftware.atlassian.net/browse/TMCU-672

Manual testing steps

Feature: Activity Perps tab and popular network filter (TMCU-602)

  Scenario: Perps returns after Solana then all popular networks without picking Ethereum
    Given the Perps feature flag is enabled
    And the user is on Activity with the transaction network filter showing popular networks
    When the user opens the network picker and selects Solana
    Then the Perps tab is hidden
    When the user opens the network picker and selects all popular networks
    Then the Perps tab is visible again
    And the picker does not show Ethereum as the sole selected chain while aggregate popular mode is intended

  Scenario: Perps still shows when directly on an EVM chain
    Given the Perps feature flag is enabled
    When the user selects an EVM network (e.g. Ethereum) from the picker
    Then the Perps tab is visible

Screenshots/Recordings

Before

See #28035

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)

Not applicable for this change (network filter / tab visibility only). Left unchecked until you validate on device if required by your release process.

• 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

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.