chore(runway): cherry-pick fix: default explore feature to enabled cp-7.64.0#25654
Merged
joaoloureirop merged 1 commit intoFeb 4, 2026
Merged
Conversation
…-7.64.0 (#25608) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** This unblocks this issue #25474 The underlying issue is that the remote feature flag controller does not reset cache on version upgrades, so users will need to close their app and wait for the feature flag cache to expire before they can see the new feature. However the remote feature flag controller change would be pretty large, so to keep the scope small (and because the explore feature is released) we will be hardcoding the feature flag to true. ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: fix: default explore feature to enabled ## **Related issues** Fixes: #25474 ## **Manual testing steps** ```gherkin 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** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** https://www.loom.com/share/a9112c646381436898a7bcd63c7ab028 ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I've included tests if applicable - [x] I've documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I've applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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. --- <a href="https://cursor.com/background-agent?bcId=bc-6a60576f-64a8-447f-843a-6d9be5062f1d"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> <a href="https://cursor.com/agents?id=bc-6a60576f-64a8-447f-843a-6d9be5062f1d"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Forces a feature flag to default-on for most builds, which can unintentionally enable UI/flows for users regardless of remote rollout state; limited scope but impacts runtime behavior. E2E behavior is explicitly preserved via `isE2E` gating. > > **Overview** > **Defaults the Explore/Trending Tokens feature to enabled** by injecting a selector-level override: `selectAssetsTrendingTokensEnabled` now forces the env override to `'true'` for non-E2E builds, bypassing remote-flag caching/version rollout delays. > > Updates tests to mock `isE2E` and refreshes `MainNavigator` snapshots to include the `ExploreSearch`, `SitesFullView`, and `BrowserTabHome` routes. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit eaed767. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Contributor
|
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. |
Contributor
🔍 Smart E2E Test Selection⏭️ Smart E2E selection skipped - base branch is not main (base: release/7.64.0) All E2E tests pre-selected. |
|
joaoloureirop
approved these changes
Feb 4, 2026
![https://cursor.com/assets/images/open-in-cursor-dark.png"><source](https://cursor.com/assets/images/open-in-cursor-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-cursor-light.png"><img](https://cursor.com/assets/images/open-in-cursor-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> <a](https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> <a){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"><source](https://cursor.com/assets/images/open-in-web-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-web-light.png"><img](https://cursor.com/assets/images/open-in-web-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"></picture></a](https://cursor.com/assets/images/open-in-web-dark.png"></picture></a){kind=link}
metamaskbot
added
the
release-7.64.0
Collaborator
|
No release label on PR. Adding release label release-7.64.0 on PR, as PR was cherry-picked in branch 7.64.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This unblocks this issue
#25474
The underlying issue is that the remote feature flag controller does not
reset cache on version upgrades, so users will need to close their app
and wait for the feature flag cache to expire before they can see the
new feature.
However the remote feature flag controller change would be pretty large,
so to keep the scope small (and because the explore feature is released)
we will be hardcoding the feature flag to true.
Changelog
CHANGELOG entry: fix: default explore feature to enabled
Related issues
Fixes: #25474
Manual testing steps
Screenshots/Recordings
Before
After
https://www.loom.com/share/a9112c646381436898a7bcd63c7ab028
Pre-merge author checklist
Docs and MetaMask Mobile
Coding
Standards.
if applicable
guidelines).
Not required for external contributors.
Pre-merge reviewer checklist
app, test code being changed).
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Note
Medium Risk
Forces a previously remote-controlled feature flag on for most builds, reducing the ability to disable the feature via remote config and potentially changing user-visible navigation behavior. Risk is limited to feature gating/UI flow, not security-critical logic.
Overview
Defaults the Explore/assets trending tokens feature on in production builds.
selectAssetsTrendingTokensEnablednow injects aforcedTrueOverride(based onisE2E) so the flag evaluates to enabled by default unless running E2E.Tests were adjusted to mock
isE2Eand preserve existing selector expectations, and theMainNavigatorsnapshots were updated to include the additional Explore-related screens (ExploreSearch,SitesFullView,BrowserTabHome).Written by Cursor Bugbot for commit 51cd2d5. This will update automatically on new commits. Configure here.
8286a85