TestFlight Procedure
This describes how a build is produced and sent. It is a procedure, not a record: whether an archive, validation or upload has happened, and with what result, is stated only in RELEASE-REPORT.md.
Preconditions
- All three test suites pass (
Scripts/test.sh core,app,ui). Scripts/l10n.py --checkreports no untranslated string.- The quality gates in checklist.md are reviewed, and every unmet gate is written down.
- The developer account has been checked (team, agreements, certificates, the bundle identifier and its capabilities) — see
docs/release/apple-developer-verification.md. - An App Store Connect record exists for
ai.spboucher.orix.audio. - The owner has explicitly authorised the upload. An upload is outward-facing and is never done on assumption.
Status, 2026-11-20. The owner authorised the first upload: build 1.0.0 (1) was validated, uploaded and processed (
VALID), and is in internal testing (group "Test"). It was uploaded before any device test, on the owner's decision; installing it from TestFlight is how that test gets done. External testing and App Review were not requested.
Identifiers and capabilities
| Item | Value |
|---|---|
| Team | 3YM54G49SN |
| App | ai.spboucher.orix.audio |
| Extension | ai.spboucher.orix.audio.widgets |
| Background mode | audio (an Info.plist key, not an entitlement) |
| Live Activities | NSSupportsLiveActivities in Info.plist; no push capability is used |
| Entitlements requiring approval | none |
Automatic signing with -allowProvisioningUpdates registers the two identifiers and creates the profiles when an App Store Connect API key with sufficient rights is supplied.
Build number
MARKETING_VERSION and CURRENT_PROJECT_VERSION are set in project.yml. App Store Connect rejects a build number it has already seen for a version: increase CURRENT_PROJECT_VERSION before every upload, and keep the extension's version in step (it uses the same settings).
Steps
xcodegen generate
# 1. Archive (Release, generic iOS device)
xcodebuild archive -project ORIXAudio.xcodeproj -scheme ORIXAudio -configuration Release \
-destination "generic/platform=iOS" -archivePath build/ORIXAudio.xcarchive \
-allowProvisioningUpdates \
-authenticationKeyPath "$ASC_KEY_PATH" -authenticationKeyID "$ASC_KEY_ID" -authenticationKeyIssuerID "$ASC_ISSUER_ID"
# 2. Export a distribution-signed IPA. The options plist (method app-store-connect, automatic signing, team 3YM54G49SN)
# is written by the release step; it is not assumed to exist in the repository.
xcodebuild -exportArchive -archivePath build/ORIXAudio.xcarchive -exportOptionsPlist Scripts/ExportOptions.plist \
-exportPath dist -allowProvisioningUpdates \
-authenticationKeyPath "$ASC_KEY_PATH" -authenticationKeyID "$ASC_KEY_ID" -authenticationKeyIssuerID "$ASC_ISSUER_ID"
# 3. Validate — uploads nothing
xcrun altool --validate-app -f dist/*.ipa -t ios --apiKey "$ASC_KEY_ID" --apiIssuer "$ASC_ISSUER_ID"
# 4. Upload — only after the owner's authorisation
xcrun altool --upload-app -f dist/*.ipa -t ios --apiKey "$ASC_KEY_ID" --apiIssuer "$ASC_ISSUER_ID"The API key identifiers and path come from the environment or a file outside the repository. .gitignore excludes *.p8, certificates, profiles and environment files.
What to check in the archive
CFBundleShortVersionStringandCFBundleVersionare the intended ones, in the app and in the extension.- The Release build contains no debug hooks:
DebugHooks.swiftand the file-input path are compiled only with theDEBUGcondition. UIBackgroundModescontainsaudio; the three usage descriptions are present;ITSAppUsesNonExemptEncryptionisfalse.PrivacyInfo.xcprivacyis in the bundle.- The icon set contains the default, dark and tinted variants.
After an upload
Statuses mean different things and are reported separately:
| Status | Meaning |
|---|---|
| Uploaded | the tool accepted the file |
| Processing | App Store Connect is processing the build |
| Processed / Valid | the build can be assigned to testers |
| Available to internal testers | assigned to an internal group; no review needed |
| Available to external testers | after Beta App Review approves the build |
Export compliance is answered by the Info.plist key. External testing needs the beta description, feedback e-mail and "What to Test" text from app-store.md.
Public release on the App Store is a separate decision and needs separate authorisation.