chore: added fingerprint status check to skip build & cache

[sethkfman]

Description

This PR updates the Android E2E build step and applies an if check on the caching and build step if the fingerprint finds a hit.

Changelog

CHANGELOG entry: null

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

^{Cursor Bugbot is generating a summary for commit e5e31e2. 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.

[github-actions]

🔍 Smart E2E Test Selection

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

click to see 🤖 AI reasoning details

The change modifies .github/workflows/build-android-e2e.yml to add conditional execution (if: steps.apk-cache-restore.outputs.cache-hit != 'true') to two steps: "Cache Gradle dependencies" and "Build Android E2E APKs". This is a pure CI build optimization that skips redundant steps when APK cache is already available.

Key observations:

1. No application code changes - Only CI workflow file modified
2. Build optimization only - The changes skip expensive build steps when cached APKs exist
3. Existing cache-hit handling - The workflow already has a "Repack APK with JS updates" step that runs when cache-hit is true, so this change just prevents the full build from running unnecessarily
4. No test logic changes - No modifications to E2E test code, fixtures, or test infrastructure
5. Straightforward conditional logic - Simple boolean condition checking cache status

This is a low-risk CI efficiency improvement. The APK building process remains unchanged when cache misses occur, and the caching logic has always intended to skip the full build on cache hits. No E2E tests need to run specifically for this change as it doesn't affect any application functionality or test behavior.

View GitHub Actions results

[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

[Cal-L]

LGTM