feat: add collapsible FF section

[sleepytanya]

Description

Changelog

CHANGELOG entry:

Related issues

Fixes:

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.

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

Low Risk
Low risk: adds a hidden (long-press) debug-only UI section and related unit tests, plus bumps build numbers across Android/iOS/CI with no changes to core wallet or security logic.

Overview
Adds a collapsible “Feature Flags” section to Settings > App Information (revealed after long-pressing the fox), showing the count of enabled remote flags, listing enabled flags alphabetically, and providing a “Copy All to Clipboard” action (JSON + confirmation alert).

Wires the screen to Redux via selectRemoteFeatureFlags and adds comprehensive unit tests covering visibility, expand/collapse behavior, ordering/filtering, and clipboard/alert interactions.

Bumps the mobile build number from 4138 to 4425 across Android versionCode, iOS CURRENT_PROJECT_VERSION, and Bitrise VERSION_NUMBER/FLASK_VERSION_NUMBER.

^{Reviewed by Cursor Bugbot for commit 280ecde. Bugbot is set up for automated code reviews on this repo. 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.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7f27880. Configure here.}

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 97%

click to see 🤖 AI reasoning details

E2E Test Selection:
All 5 changed files represent low-risk, isolated changes:

1. android/app/build.gradle: Pure version code bump (4138 → 4425). No functional changes, no E2E test impact.

2. ios/MetaMask.xcodeproj/project.pbxproj: Pure version code bump (4138 → 4425) across 6 build configurations. No functional changes, no E2E test impact.

3. bitrise.yml: CI version number update (4138 → 4425) for main and Flask builds. No workflow logic changes, no E2E test impact.

4. app/components/Views/Settings/AppInformation/index.js: Adds a Feature Flags display section to the App Information settings screen. This is a developer/debug feature hidden behind a long-press gesture on the fox icon. It reads remote feature flags from Redux state and displays enabled ones. This is completely isolated to the Settings > App Information screen, doesn't affect any shared components (navigation, modals, confirmations, accounts, networks), and has no impact on any user-facing flows tested by E2E suites.

5. app/components/Views/Settings/AppInformation/index.test.tsx: Unit tests for the new feature flags display. No E2E impact.

No E2E tags are warranted because:

• No changes to core flows (transactions, swaps, accounts, networks, onboarding)
• No changes to shared components (TabBar, navigation, modals, confirmations)
• No changes to controllers or Engine
• The AppInformation change is a debug-only UI addition in a deeply nested settings screen
• All changes are well-covered by the accompanying unit tests

Performance Test Selection:
No performance impact expected. The AppInformation settings screen change is a simple UI addition (feature flags list) hidden behind a long-press gesture. Version bumps and CI changes have no performance implications. No changes to rendering-intensive components, data loading, state management, or critical user flows.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud