fix(network-enablement-controller): add Tempo to POPULAR_NETWORKS so "All popular networks" selects correctly

[vinnyhoward]

Explanation

Problem: The "All popular networks" row in the network multi-selector does not highlight after being tapped for users who have the Tempo network (chain ID 4217 / 0x1079) configured in their wallet.

Root cause: The app's PopularList (app/util/networks/customNetworks.tsx) includes Tempo, so it shows up in the popular-networks UI via selectPopularNetworkConfigurationsByCaipChainId. However, the controller's enableAllPopularNetworks() only enables networks listed in POPULAR_NETWORKS (packages/network-enablement-controller/src/constants.ts), which was missing Tempo. As a result, areAllEvmNetworksSelected stayed false even after tapping "All popular networks" — leaving the aggregate row unhighlighted while every individual network row appeared highlighted instead.

Migration 132 in MetaMask Mobile confirms a subset of users already have Tempo configured from prior use, so this affects real users in the wild.

Fix: Add '0x1079' (Tempo, chain ID 4217) to POPULAR_NETWORKS so that enableAllPopularNetworks() enables Tempo alongside the other popular networks, keeping the controller's notion of "all popular" in sync with the UI's PopularList.

Expected behavior after fix: Tapping "All popular networks" highlights the aggregate row and deselects the individual rows.

References

• TMCU-857
• app/util/networks/customNetworks.tsx (MetaMask Mobile) — PopularList includes Tempo (0x1079)
• packages/network-enablement-controller/src/constants.ts — POPULAR_NETWORKS (was missing Tempo)
• Migration 132 (MetaMask Mobile) — adds Tempo to existing users' network configurations

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Low Risk
Single constant and changelog entry; no logic changes beyond including one more chain in the existing popular-networks list.

Overview
Adds Tempo (0x1079, chain ID 4217) to POPULAR_NETWORKS in constants.ts and documents it under Unreleased in the package changelog.

That aligns enableAllPopularNetworks() (and related “all popular EVM” checks) with the client popular-networks list, so the “All popular networks” aggregate row can highlight correctly when Tempo is configured instead of leaving areAllEvmNetworksSelected false.

^{Reviewed by Cursor Bugbot for commit 98f707f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Prithpal-Sooriya]

just wanna double check. Popular networks doesn't mean default right? It should appear as an "additional network"?

Just being overly cautious :)

[vinnyhoward]

In this context it is a popular network, I've made that assumption because it was recently added into mobile and it appears as popular. I've attached a video below showing Tempo in popular networks. Also, its showcasing the bug explained in the PR description @Prithpal-Sooriya

If this is incorrect I'm happy to fix the issue or close the PR and come up with another solution. I just need more context on the Tempo network addition

Simulator.Screen.Recording.-.iPhone.17.-.2026-06-10.at.15.38.15.mov