Wsun/test fingerprint

[weitingsun]

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.

[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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

🔍 Smart E2E Test Selection

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

click to see 🤖 AI reasoning details

After analyzing the changed files, this PR is focused entirely on OTA (Over-The-Air) update infrastructure and Expo Updates configuration. The changes include:

1. Build & CI/CD Configuration (package.json, app.config.js, bitrise.yml, .github/workflows/push-eas-update.yml): Configuration for OTA updates and build pipelines
2. Platform-specific Build Files (android/app/build.gradle, ios/MetaMask.xcodeproj/project.pbxproj): Native build configurations
3. OTA Update Scripts (scripts/update-expo-channel.js): Script for managing Expo update channels with code signing
4. Code Signing Certificate (certs/certificate.pem): Certificate for signing OTA updates
5. Minor UI Change (app/components/Views/Settings/AppInformation/index.js): Commented out fox logo long-press handler, displays OTA update information

Why No Tags Selected:

• These are infrastructure and build system changes that don't modify wallet functionality
• No changes to core wallet features, Controllers, Engine, or user flows
• The only user-facing change is in the Settings > About screen showing OTA update info (minor, non-critical)
• OTA update mechanism is deployment infrastructure, not a testable feature through E2E tests
• Build configuration changes (Gradle, Xcode project, CI config) don't affect runtime behavior that E2E tests would catch

Risk Assessment:

• Low Risk: Infrastructure changes are isolated from user-facing functionality
• Changes are configuration-focused and well-contained
• No modifications to transaction flows, account management, network switching, or other critical user paths

Confidence:

• 85% confidence - While I've thoroughly analyzed the files, I cannot see the actual diff content to confirm 100% of the changes. However, based on file content and the nature of OTA update infrastructure work, I'm confident these changes don't require E2E testing as they're not testing user-facing features but rather deployment mechanisms.

View GitHub Actions results