TestFlight & App Store

Preparation Checklist

• Versioning: Increment Version (marketing) and Build numbers.
• Signing: Bundle ID, Team, and capabilities configured; profiles/certificates valid.
• Info.plist: Required NS*UsageDescription keys present (Camera, Photos, etc.).
• Privacy: App Privacy details ready (data collection, tracking); privacy policy URL.
• Assets: App icon in Assets; required screenshots prepared.
• Encryption: Know if your app uses encryption (export compliance questions later).

---

Archive and Upload

In Xcode, choose Product → Archive.

In Organizer, validate and upload the build to App Store Connect.

This creates a signed archive and sends it to App Store Connect where you manage TestFlight and submissions.

• Use Distribute App in Organizer → App Store Connect → Upload.
• Ensure symbols are included for crash symbolication.
• Wait a few minutes for processing; the build will appear under TestFlight in App Store Connect.

Example

Product → Archive
Organizer → Distribute App → App Store Connect → Upload
✓ Include symbols for symbolication
After processing: App Store Connect → TestFlight → Builds

---

TestFlight Testing

• Internal testers (up to 100): Team members in App Store Connect can access builds immediately.
• External testers (up to 10,000): Requires Beta App Review for the first build of a version.
  • Add testers by email or enable a public link.
  • Provide Test Information (what to test, demo account) for reviewers/testers.
  • Answer Export Compliance questions (encryption) when prompted.
• Build notes & groups: Create groups, attach builds, and write per-build notes for context.
• Expiry & feedback: Builds expire after 90 days; feedback and crash logs appear in App Store Connect.

---

App Store Submission

• Create/complete app record: Metadata, category, age rating, pricing/availability.
• Privacy: App Privacy “Data Collection” answers and privacy policy URL.
• Compliance: Export compliance (encryption) and content rights if applicable.
• Select build: On the version page, choose the processed build and Submit for Review.
• Release: After approval, release immediately or use Phased Release.