React Native and Expo provide modern JavaScript and TypeScript development environments for crafting cross-platform applications. Today, developers increasingly build React Native and Expo apps with AI coding assistants like Cursor, Claude Code, and Antigravity.
However, delivering code to real iPhone users requires packaging the application into a cryptographically signed iOS binary (.ipa) and delivering it to Apple's App Store Connect servers.
Historically, publishing to App Store Connect required either launching Xcode to run interactive Organizer wizards, or delegating automated submissions to cloud services such as Expo's EAS Submit.
This guide demonstrates a local-first, terminal-centric workflow: generate your signed .ipa locally (or via EAS Build), download it to your workspace, inspect the archive with your AI assistant using FlightDeck to catch configuration mistakes before upload, and deliver it directly to App Store Connect without leaving your editor.
Architectural Overview: EAS Build vs. Local FlightDeck Delivery
Both Expo EAS and FlightDeck offer modern CLI-driven pipelines, but they serve different architectural workflows:
Workflow A: Expo EAS Submit (Managed Cloud CI/CD)
[Source Code] ──► [EAS Cloud Build] ──► [EAS Submit Service] ──► [Apple API]
(Credentials stored securely in Expo Cloud Secret Store)
Workflow B: Local AI-Assisted Upload (FlightDeck)
[Source Code] ──► [Bare Xcodebuild or EAS Build] ──► [Local Signed .ipa]
│
AI Prompt + FlightDeck ▼
[Local Developer Mac] ──► [Apple Transport Storage]
(App Store Connect API Keys remain on local machine)
| Architectural Dimension | Expo EAS Submit | FlightDeck Local Delivery |
|---|---|---|
| Workflow Focus | Automated cloud CI/CD pipelines | Local pair programming with AI agents |
| Credential Posture | Stored securely in Expo cloud secrets | Stored strictly in local developer keychain / config |
| Pre-Upload Inspection | Evaluated during cloud job execution | Inspected locally in editor before network transfer |
| Assistant Integration | Terminal CLI commands (eas submit) |
Natural-language AI prompts in Cursor, Claude, Antigravity |
| Safety Governance | CI configuration parameters | FlightDeck Desktop Approval Center with staged proposals |
EAS Cloud Artifact Download Requirement: FlightDeck does not compile JavaScript, manage Expo cloud secrets, or automatically download remote build artifacts from Expo's servers. If you use Expo Cloud Build (eas build -p ios), you must download the generated .ipa to your local project directory before prompting FlightDeck to inspect or deliver it.
Generating Your Signed .ipa Binary
Choose the packaging method that fits your project architecture: Expo Application Services (EAS) or Bare React Native.
Option A: Expo Projects (EAS Build)
If you manage your project with Expo, you can build either locally or using EAS cloud workers.
1. Local EAS Build (Requires macOS with Xcode)
npx eas-cli build --platform ios --profile production --local --output=./build/MyApp.ipa
2. Cloud EAS Build
npx eas-cli build --platform ios --profile production
When the cloud build finishes, download the resulting .ipa file to your project directory (for example, ./build/MyApp.ipa). You can download it directly from the build URL displayed in your terminal or via Expo's web dashboard.
Ensure your app.json specifies explicit version numbers to prevent Apple ingestion rejections:
```json
{
"expo": {
"name": "My App",
"slug": "my-app",
"version": "1.0.0",
"ios": {
"bundleIdentifier": "com.example.myapp",
"buildNumber": "1"
}
}
}
```
Option B: Bare React Native Projects
For bare React Native projects (without Expo managed workflow), produce the signed archive using Xcode CLI tools:
1. Install CocoaPods Dependencies
cd ios && pod install && cd ..
2. Create ios/ExportOptions.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>app-store</string>
<key>signingStyle</key>
<string>automatic</string>
<key>stripSwiftSymbols</key>
<true/>
<key>uploadSymbols</key>
<true/>
</dict>
</plist>
3. Archive and Export
# Archive the workspace
xcodebuild archive \
-workspace ios/MyApp.xcworkspace \
-scheme MyApp \
-configuration Release \
-archivePath build/ios/MyApp.xcarchive
# Export the IPA
xcodebuild -exportArchive \
-archivePath build/ios/MyApp.xcarchive \
-exportOptionsPlist ios/ExportOptions.plist \
-exportPath build/ios/ipa
The exported binary is saved to build/ios/ipa/MyApp.ipa.
Inspecting and Uploading the Binary with Your AI Coding Assistant
Once the .ipa is saved on your local machine, you can manage the verification and delivery sequence using natural language with your connected AI coding assistant.
Step 1: Pre-Upload Inspection Prompt
Ask your assistant to confirm the intended app and inspect the archive:
I have a React Native iOS release build located at [path/to/app.ipa]. Use FlightDeck to inspect the binary, verify the bundle identifier, marketing version, and build counter against App Store Connect for [Your App Name], and confirm it is ready for upload.
Behind the scenes, FlightDeck executes an offline check (build_upload_preview) without sending the binary across the network:
- Confirms the ZIP archive contains a valid
Payload/*.appbundle. - Reads
Info.plistto extract bundle ID, version, and build numbers. - Checks that the bundle ID matches your registered App Store Connect application.
- Verifies that the package structure is valid and non-corrupt.
Step 2: Upload Delivery Prompt
Once the inspection confirms the binary is sound and correctly targets your app, prompt your assistant to stage the upload:
The archive looks valid. Stage an upload of [path/to/app.ipa] to App Store Connect for [Your App Name] using FlightDeck.
Because delivering a new binary creates resources on Apple's servers, FlightDeck stages the request and displays the Approval Center sheet in FlightDeck Desktop:
Illustrative representation of the FlightDeck Approval Center sheet:
┌──────────────────────────────────────────────────────────────┐
│ FlightDeck Desktop — Operation Approval Request │
├──────────────────────────────────────────────────────────────┤
│ Operation: Deliver iOS Binary (.ipa) │
│ Target App: [Your App Name] (App ID: 6812899314) │
│ File Path: ./build/MyApp.ipa │
│ Version: 1.0.0 (Build 34) │
│ Platform: iOS │
│ Action: Upload binary parts to Apple Ingestion Storage │
│ Impact: Stages build for Apple server processing. │
├──────────────────────────────────────────────────────────────┤
│ [Reject Proposal] [Approve & Execute] │
└──────────────────────────────────────────────────────────────┘
Review the parameters in FlightDeck Desktop and click Approve & Execute. FlightDeck streams the binary in chunked parts directly to Apple's ingestion storage.
Tracking Apple Ingestion and Processing Status
Once the upload transfer completes, Apple's cloud workers validate and process the binary. You can monitor progress through conversational follow-ups.
Monitoring Prompt
Check the status of our recently uploaded React Native build in App Store Connect. Has Apple finished processing build [e.g., 34], and is it marked VALID?
Your assistant queries App Store Connect and reports:
- The current processing state (
PROCESSING,VALID, orINVALID). - Whether the build has completed Apple's automated binary scanning.
- Whether export compliance is blocking distribution.
When the build reaches VALID, it is ready to be distributed to TestFlight beta groups or attached to an App Store release draft.
Common React Native and Expo Upload Pitfalls
1. Missing Export Compliance Declaration
If your build shows "Missing Compliance" in TestFlight, declare the non-exempt encryption status in your project configuration:
In Expo app.json:
{
"expo": {
"ios": {
"config": {
"usesNonExemptEncryption": false
}
}
}
}
In bare React Native ios/MyApp/Info.plist:
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
(Only declare false if your app's actual cryptographic usage qualifies for exemption under U.S. EAR regulations. See Fixing Missing Encryption Key (ITSAppUsesNonExemptEncryption).)
2. Build Number Collisions
Apple requires a strictly higher build counter for every upload of a given version:
- When using EAS, enable automatic incrementing in
eas.json: ``json { "build": { "production": { "autoIncrement": true } } }`` - In bare React Native, increment
CURRENT_PROJECT_VERSIONbefore creating a new archive.
3. Shipping Metro Development Bundles
In bare React Native projects, verify that your scheme configuration is set to Release, not Debug. Debug archives include Metro development URLs and will fail to launch on physical devices disconnected from your local machine.
Summary Checklist and Next Steps
| Stage | Action | Tool / Method |
|---|---|---|
| 1. Package .ipa | Generate signed production archive via EAS or Xcode CLI. | eas build or xcodebuild |
| 2. Save Locally | Ensure .ipa is saved in your local workspace directory. |
Local Filesystem |
| 3. Inspect Offline | Prompt AI assistant to verify metadata and package integrity. | FlightDeck conversational prompt |
| 4. Approve Delivery | Review and authorize upload in FlightDeck Desktop. | FlightDeck Approval Center |
| 5. Monitor Processing | Track transition from PROCESSING to VALID. |
Follow-up status prompt |
Related Resources
- Pre-Upload Binary Inspection: How FlightDeck Validates .ipa Files
- Why Is My TestFlight Build Stuck on Processing? Causes and Fixes
- Fixing Missing Encryption Key (ITSAppUsesNonExemptEncryption)
- Automating TestFlight Beta Distribution from Your AI Coding Assistant
- Expo Documentation: Building iOS Apps