testflight_skill

Overview

This skill helps you distribute iOS and macOS beta builds via TestFlight, manage tester groups, and automate uploads through CI/CD. It packages practical guidance for App Store Connect setup, build requirements, upload methods, and common traps to avoid. The content prioritizes secure API usage and repeatable automation patterns.

How this skill works

The skill inspects and documents the end-to-end TestFlight workflow: App Store Connect prerequisites, build signing and provisioning, tester group strategies, and upload options (Xcode, altool, fastlane, Xcode Cloud, Transporter). It outlines CI/CD setup using App Store Connect API keys and example fastlane and xcrun commands, plus security recommendations for keys and credentials. It also highlights typical failures and remediation steps to keep your pipeline healthy.

When to use it

• You need to distribute beta builds to internal or external testers via TestFlight.
• You want to integrate TestFlight uploads into CI/CD (fastlane, xcrun, or Xcode Cloud).
• You need a checklist for App Store Connect setup and build signing before upload.
• You want to manage tester groups and understand Apple review requirements.
• You need to troubleshoot common TestFlight upload or processing failures.

Best practices

• Create the App and register the Bundle ID in Developer Portal before uploading.
• Always increment CFBundleVersion (build number) for every upload; never reuse numbers.
• Prefer App Store Connect API keys (App Manager role) in CI to avoid 2FA and app-specific password issues.
• Validate provisioning profiles and export compliance answers before archiving.
• Use internal testers for fast iteration; submit to external testers only after a stable build and review readiness.
• Plan around the 90-day TestFlight build expiration and Apple review windows.

Example use cases

• Automate nightly beta builds with fastlane using an App Store Connect API key for upload_to_testflight.
• Quick manual upload for a hotfix via Xcode or Transporter when CI is not available.
• Set up internal tester groups for QA and only push to external testers after passing internal validation.
• Integrate xcrun altool in a lightweight CI script when fastlane is not needed.
• Troubleshoot a stuck processing build by checking export compliance and provisioning profile validity.