mega-fastlane-metadata

MEGA iOS Fastlane & App Store Metadata

All bundle exec fastlane commands run from the project root directory.

---

Jenkins CI Trigger Phrases

Post these as comments on the relevant GitLab MR to trigger Jenkins jobs.

---

Fastlane Lanes Reference

Build & Archive

Versioning

Upload & Distribution

Metadata (App Store Connect)

Testing

Developer Setup

---

Screenshots: Update Workflow

Step 1 — Download Current Screenshots

bundle exec fastlane deliver download_screenshots

Downloads into fastlane/screenshots/ organized by language folder (e.g. ar-SA/, en-US/).

Step 2 — Swap Screenshots

• Replace images in the appropriate language folder
• iPad Pro 12.9" files must include ipadPro129 in the filename (e.g. ipadPro129_1.png) so Fastlane assigns the correct display family
• Replace screenshots as directed by the Design team

Step 3 — Upload New Screenshots

bundle exec fastlane deliver app_version:"<X.Y>" force:true skip_binary_upload:true overwrite_screenshots:true skip_metadata:true

Note: overwrite_screenshots only works correctly if the new filenames match the downloaded ones. If filenames differ, either rename the new files or remove screenshots from the version in App Store Connect first.

---

Signing Certificates

MEGA uses fastlane match to manage all signing. Certs are stored encrypted in the internal iOSCertificates GitLab repo.

Rules:

• Never use "Automatically manage signing" in Xcode — it modifies the project file
• Never manually push changes to iOSCertificates — always use fastlane commands

Sync Certs to Local (Read-Only)

# Development (needed when debugging on a device)
bundle exec fastlane cert_dev readonly:true

# QA / AdHoc (rarely needed locally)
bundle exec fastlane cert_qa readonly:true

# App Store (rarely needed locally)
bundle exec fastlane cert_appstore readonly:true

Register a New Test Device

Preferred: via CI

1. Invite the user to the internal-testers group on Crashlytics (not "all testers")
2. Ask the user to follow the invitation email on the new device to register it
3. Crashlytics collects the UDID and sends it via email
4. Trigger a build on an empty MR with the comment:

   deliver_qa_include_new_devices
   

   MR title: *DO NOT MERGE* To add test device
5. Sync dev certs to local for debugging (check match passcode with your lead):

   bundle exec fastlane cert_dev readonly:true
   

Manual (appops only — use only if CI fails):

bundle exec fastlane run register_device udid:"1234…890" name:"Mike's test iPhone"
bundle exec fastlane cert_dev readonly:false
bundle exec fastlane cert_qa readonly:false

Check with your lead for access to the appops user.

Update All Signing Certificates (appops only)

Must be run using appops@mega.co.nz account.

# Step 1: Nuke (revokes all certs and profiles)
fastlane match nuke <type>   # type: development | adhoc | appstore

# Step 2: Regenerate
bundle exec fastlane all_certs

# Step 3: Set a reminder
# Post in #mobile-dev-team 2 weeks before the next expiration date

Update Some Certificates (appops only)

1. Revoke the expired/expiring certs on App Store Connect
2. Delete them from the iOSCertificates repo at https://code.developers.mega.co.nz/mobile/ios/iOSCertificates
3. Regenerate:

   bundle exec fastlane all_certs readonly:false
   

   (Run as appops@mega.co.nz)
4. Sync certs to local (see Sync Certs section above)

---

Configuration Files

Bundle ID Mapping

---

App Store Submission (Jenkins Job)

The App Store submission job (iOS-Submit-App-Store) is run by the DevOps / Secure Systems team — not directly by the release captain.

The release captain provides the job parameters via the #devops-cicd Slack message (see /mega-release-workflow Phase 3):

• Job URL: https://controller.cibuild.mega.co.nz/job/iOS/job/iOS-Submit-App-Store/
• Parameters: MR Number, Version Number, Build Number
• Hotfix only: 7-day phased: false