TestFlight release procedure
The steps to produce and send a build. The outcome of each step for the current build is recorded in RELEASE-REPORT.md; this document never states that a step succeeded.
Rules
- No upload without the owner's explicit authorization for that build.
Scripts/release.sh uploadrefuses to run unlessORIX_UPLOAD_AUTHORIZED=yesis set. - No public App Store submission and no external (beta-review) testing without a separate authorization.
- Signing material and the App Store Connect API key never enter the repository. The key id and issuer id are read from
~/.config/orix-secure/asc.env; the.p8stays in~/.appstoreconnect/private_keys/. - Statuses are reported with Apple's own words: uploaded, processing, VALID, internal testing available, external testing available.
Sequence
| # | Step | Command / place | Evidence to record |
|---|---|---|---|
| 1 | Engine tests | Scripts/build.sh kit |
One "Test run with N tests … passed" line per package |
| 2 | UI tests, iPhone and iPad | Scripts/build.sh uitest, ORIX_SIM="ORIXSecure iPad" Scripts/build.sh uitest |
"Executed N tests, with 0 failures" |
| 3 | Hygiene | Scripts/check.sh |
clean |
| 4 | Localization complete | Scripts/localize.py |
"N keys … N translated" with exit code 0 |
| 5 | Apple Developer account checked in Safari | https://developer.apple.com/account | Team, membership, identifiers (owner signed in) |
| 6 | App record | App Store Connect › Apps | Apple ID of the record, bundle ID, SKU |
| 7 | Bump build number | CURRENT_PROJECT_VERSION in project.yml |
— |
| 8 | Archive (Release, device) | Scripts/release.sh archive |
version (build), signing identity, team |
| 9 | Export for App Store Connect | Scripts/release.sh export |
.ipa size |
| 10 | Validate | Scripts/release.sh validate |
altool's verdict, quoted |
| 11 | Owner's authorization | — | Date and wording |
| 12 | Upload | ORIX_UPLOAD_AUTHORIZED=yes Scripts/release.sh upload |
Delivery UUID |
| 13 | Processing | App Store Connect › TestFlight | Processing state, then VALID or the rejection reason |
| 14 | Internal group | App Store Connect › TestFlight › Internal Testing | Group name, tester state |
Capabilities the provisioning profile must carry
com.apple.developer.networking.wifi-info(Access Wi‑Fi Information) onai.spboucher.orix.secure. Automatic signing with-allowProvisioningUpdatesregisters it.- The share extension
ai.spboucher.orix.secure.shareneeds its own App ID and profile (no extra capability).
No app group, no iCloud, no push, no NetworkExtension provider, no associated domains.
Release notes (build 1)
English First TestFlight build of ORIX Secure. Please try, on a real device: the security audit and checklist, Photo Cleanup on your own library (nothing is deleted without two confirmations), the link analyser including the share-sheet "Analyse Link" action and QR scanning, Network Lab (Wi‑Fi security type needs Location permission), App Lock. Report anything that looks like a claim the app cannot back up.
Français Première version TestFlight d’ORIX Secure. À essayer sur un appareil réel : l’audit de sécurité et la liste de vérification, le nettoyage des photos sur votre propre photothèque (rien n’est supprimé sans deux confirmations), l’analyse de liens, y compris l’action « Analyser le lien » de la feuille de partage et la lecture de codes QR, le laboratoire réseau (le type de sécurité du Wi‑Fi exige l’autorisation de localisation) et le verrouillage de l’app. Signalez toute affirmation que l’app ne pourrait pas justifier.
What to test on a device first
The Simulator cannot exercise these; they are the purpose of the first TestFlight build: battery readings, Secure Enclave / App Attest / data-protection findings, camera QR scanning, Wi‑Fi security type, the Local Network prompt, App Lock with Face ID, Photo Cleanup speed and memory on a large library with iCloud originals, VoiceOver.