🚀 Build, upload & processing

Build the App Store package from the CLI:

1. Run the build (below). Output lands in build/ios/ipa/.
2. flutter build ipa archives and exports for App Store distribution in one shot. If you prefer the Xcode UI, flutter build ipa still leaves an .xcarchive in build/ios/archive/ you can open in Organizer.
3. Upload the .ipa with the Transporter app (Mac App Store) or xcrun altool — or open the archive in Xcode Organizer and use Distribute App (next step).

flutter build ipa --release

xcrun altool --upload-app -f build/ios/ipa/*.ipa -t ios -u you@example.com -p "abcd-efgh-ijkl-mnop"

1. In Xcode, set the run destination to Any iOS Device (arm64) — Product → Archive is greyed out while a simulator is selected.
2. Product → Archive. The build compiles in Release and the Organizer window opens with your archive.
3. Select the archive → Distribute App → App Store Connect → Upload (newer Xcode condenses this into a single 'App Store Connect' distribute option).
4. Keep the defaults: include symbols, let Xcode manage signing for distribution.
5. Xcode validates and uploads. 'Upload Successful' means it reached Apple — processing happens next and can still fail silently (see the processing step).

Keep the archive: Organizer retains your dSYMs, which you'll need to symbolicate crash logs from review.

1. Submit your latest EAS build straight from the cloud:
2. First run, EAS asks for an App Store Connect API key (recommended — create at Users and Access → Integrations) or an app-specific password, and can create the App Store Connect app record for you if it doesn't exist.
3. eas submit picks your most recent finished build by default; pass --id <build-id> for a specific one.
4. Alternative: download the .ipa from the EAS build page and upload manually with Apple's Transporter app.

One-liner for the impatient: eas build --platform ios --auto-submit builds and submits in one go.

eas submit --platform ios

eas build --platform ios --profile production --auto-submit

Every build must answer the US export-compliance question about encryption.

• Apps using only standard HTTPS/TLS (i.e. Apple's built-in encryption, no custom crypto): you qualify for the exemption — answer that you use standard/exempt encryption. This is the answer for the vast majority of apps.
• Apps with proprietary encryption may need to file annual self-classification reports with the US government — talk to a professional.

Skip the question forever by pre-answering in Info.plist with ITSAppUsesNonExemptEncryption = false — then App Store Connect won't ask on every single build:

<key>ITSAppUsesNonExemptEncryption</key>
<false/>

{
  "expo": {
    "ios": {
      "infoPlist": { "ITSAppUsesNonExemptEncryption": false }
    }
  }
}

After upload, Apple runs post-processing validation (malware scan, API/entitlement checks, asset validation).

• Normal duration: 15–60 minutes. Release-season peaks can stretch to a few hours.
• The build appears in App Store Connect → your app → TestFlight tab when done; you'll also get a 'completed processing' email.
• Only processed builds can be selected for TestFlight or review submission.

While waiting, this is a great time to finish metadata or screenshots — don't sit refreshing.