feat(qa-build): update pipeline for generating ios and android builds

[alucardzom]

Description

This PR introduces GitHub Actions workflows for testing iOS and Android QA app builds, providing automated build testing and artifact management capabilities similar to our existing Bitrise workflows.

Workflow Triggers

Workflow	Trigger Type	When It Runs
iOS Build	workflow_dispatch	Manually from GitHub Actions UI with custom inputs
Android Build	workflow_dispatch	Manually from GitHub Actions UI with custom inputs

Workflow Inputs

Workflow	Input Name	Description	Type	Required	Default
iOS Build	retention_days	Number of days to retain the uploaded artifacts	string	❌ No	'7'
Android Build	retention_days	Number of days to retain artifacts	string	❌ No	'7'

Workflow Triggers

Workflow	Trigger Type	When It Runs
iOS Build	workflow_dispatch	Manually from GitHub Actions UI with custom inputs
Android Build	workflow_dispatch	Manually from GitHub Actions UI with custom inputs

Key Features

• ✅ iOS QA Build Testing: Automated simulator builds with comprehensive artifact uploads (.app, .ipa, .xcarchive, source maps)
• ✅ Android QA Build Testing: Automated APK and AAB bundle generation with artifact uploads
• ✅ Manual Workflow Triggers: Workflows can be executed manually from GitHub Actions UI on any branch
• ✅ Configurable Artifact Retention: Customizable artifact retention period with descriptive input (default: 7 days)
• ✅ Optimized CI Setup: Enhanced setup.mjs script with GitHub CI optimizations
• ✅ Comprehensive Artifact Collection: Uploads apps, archives, source maps with detailed status reporting
• ✅ Graceful Error Handling: Continues workflow execution even if optional artifacts fail
• ✅ Step-by-Step Documentation: Clear comments explain each workflow step's purpose

Added

• New GitHub Actions workflow: .github/workflows/test-ios-build-app.yml
  • Builds iOS QA app for simulator (MetaMask-QA.app)
  • Attempts to upload device artifacts (.ipa, .xcarchive) when available
  • Collects iOS source maps for debugging
• New GitHub Actions workflow: .github/workflows/test-android-build-app.yml
  • Builds Android QA APK for device installation
  • Generates Android App Bundle (AAB) for distribution
  • Collects Android source maps for crash tracking
• Manual workflow dispatch triggers with configurable artifact retention period
• Comprehensive artifact upload capabilities with detailed status reporting
• Workflow outputs for artifact URLs and upload status tracking
• Inline comments documenting each workflow step's purpose

Changed

• Updated scripts/setup.mjs to optimize for GitHub CI environments
• Added GITHUB_CI flag support for conditional setup steps in PPOM build
• Enhanced PPOM build process with optional clean/install steps in CI
• Modified setup script to skip unnecessary operations in CI environments
• Improved memory allocation for GitHub runners with NODE_OPTIONS=--max_old_space_size=4096

Changelog

CHANGELOG entry: null

Related issues

Manual testing steps

Prerequisites

• Ensure you have necessary GitHub secrets configured:
  • SEGMENT_WRITE_KEY_QA, SEGMENT_PROXY_URL_QA, SEGMENT_DELETE_API_SOURCE_ID_QA
  • MM_SENTRY_DSN_TEST, MM_SENTRY_AUTH_TOKEN
  • GOOGLE_SERVICES_B64_IOS, GOOGLE_SERVICES_B64_ANDROID
  • OAuth client IDs for testing environments

Testing iOS Workflow

• Navigate to Actions tab → Test iOS Build QA App
• Click Run workflow button
• Configure workflow inputs:
• Branch: Select your desired branch
• Retention days: Enter number of days to retain artifacts (e.g., "14" for 2 weeks)
• Click Run workflow and monitor execution progress
• Verify the following steps were completed successfully:
  • ✅ iOS environment setup and tool installation
  • ✅ Project setup and dependency installation
  • ✅ iOS QA app build for simulator
  • ✅ Artifact uploads (APP will succeed, IPA/Archive may skip without certificates)
• Download artifacts from the workflow run summary page
• Test the downloaded MetaMask-QA.app file in iOS Simulator

Testing Android Workflow

• Navigate to Actions tab → Test Android Build QA App
• Click the Run workflow button
• Configure workflow inputs (branch and retention period)
• Monitor build execution and verify these steps:
  • ✅ Android SDK and environment setup
  • ✅ Project setup and dependency installation
  • ✅ Android QA APK and AAB bundle generation
  • ✅ All artifact uploads (APK, AAB, source map)
• Download artifacts from the workflow summary
• Install and test the app-qa-release.apk file on an Android device/emulator
• Optionally, validate the AAB bundle for distribution compatibility

Screenshots/Recordings

Android Build and Upload

iOS Build and Upload

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.

[alucardzom]

This must be updated once MetaMask/github-tools#85 is merged.

[alucardzom]

This should be removed, added for testing into this branch

[alucardzom]

This should be removed, added for testing into this branch

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

Hi @alucardzom,

on the day following feat or perf PR merge, PM and author to test changes on main (feature + exploratory around the edges) using the latest nightly build with casual user persona and also a power user persona where performance might be a challenge. Please record the testing in a video, check the relevant post-merge checklist box below, and post the video in a comment at the bottom of this PR.

Author validation checklist

• Validated the changes in main branch using the nightly build
• Video shared

PM validation checklist

• Validated the changes in main branch using the nightly build
• Video shared