Overview: Orchestrating App Review Submissions via Chat
Submitting an iOS application to Apple App Review is the defining milestone of your release cycle. Traditionally, completing a submission meant navigating multiple screens in the App Store Connect web portal: selecting an uploaded build, confirming export compliance, checking screenshot sets across device sizes, verifying pricing and availability, and clicking the blue "Submit to App Review" button.
With FlightDeck connected to your AI coding assistant (Cursor, Claude Code, Xcode with MCP, or Antigravity), you can orchestrate this entire preparation, pre-flight, and submission pipeline through natural-language conversation.
However, release submission carries real operational consequences: an accidental submission with an unvalidated binary, incomplete metadata, or broken demo credentials risks immediate rejection by Apple, resetting your position in the review queue. To prevent unintended dispatches, FlightDeck enforces a strict distinction between draft preparation (which gathers and validates release assets) and binding submission (which requires explicit confirmation in FlightDeck's native macOS Desktop Approval Center).
Developer Prompt: "Prepare and submit version 1.2.0 for App Review"
│
▼
[Step 1-6: Autonomous Staging & Verification]
Assistant checks version, builds, screenshots,
creates ReviewSubmission draft, and runs preflight
│
▼
[Step 7: FlightDeck Desktop Approval Center]
Developer reviews SHA-256 bound submission card
│
┌───────┴───────┐
▼ ▼
[Approve] [Reject]
│ │
▼ ▼
[Step 8: Direct Apple HTTPS] [Submission Aborted]
Dispatches to reviewSubmissions
│
▼
[Step 9: State -> WAITING_FOR_REVIEW]
The Primary Prompt: Prepare and Submit for App Review
Connect your AI coding assistant to FlightDeck and paste the following prompt:
Please prepare and stage an App Store Review submission for my app using FlightDeck:
1. Dynamically locate my app record and inspect the active version draft in PREPARE_FOR_SUBMISSION.
2. Confirm that a valid TestFlight build is attached and that all preflight readiness checks pass (screenshots, descriptions, URLs, demo credentials).
3. Check if an active ReviewSubmission container already exists for iOS. If not, stage a new review submission draft.
4. Attach the active version draft to the submission container and run preflight submission checks.
5. Present a clear summary of the staged submission in chat, including the app name, version, attached build number, and preflight status.
6. Do NOT trigger the final binding submission to Apple until I review the summary and explicitly approve it.
The 9-Stage Submission Pipeline
FlightDeck guides your release through a nine-stage pipeline designed for safety, auditability, and clear separation of concerns:
Stage 1: Inspect App and Candidate Version Draft
Your assistant calls apps_list and app_store_versions_list to resolve your application record and confirm an editable release draft exists in PREPARE_FOR_SUBMISSION state.
Prompt: "Which App Store version draft is currently open for my app?"
Your assistant identifies the version string (e.g., 1.2.0) and confirms its state allows editing.
Stage 2: Audit Release Prerequisites
Before assembling the review envelope, your assistant invokes release_readiness_check to verify:
- At least one screenshot is uploaded for each required display size (6.7" iPhone, 12.9" iPad for universal apps).
- Localized description, keywords, and support URLs are populated.
- App Privacy Policy HTTPS URL is configured.
- Age rating declaration is complete.
- Reviewer contact details (name, phone, email) and demo login credentials (if applicable) are provided.
Stage 3: Confirm or Attach Valid Build
The version draft must be linked to a processed binary with status VALID and export compliance cleared.
Prompt: "List available candidate builds for version 1.2.0 and verify whether a valid build is currently attached."
If no build is attached, your assistant stages build selection via release_build_select, which you confirm in FlightDeck's Approval Center.
Stage 4: Check for Existing Submissions
Apple permits only one active ReviewSubmission container per platform at a time. Your assistant queries review_submissions_list:
- If an existing submission is already
WAITING_FOR_REVIEWorIN_REVIEW, a new submission cannot be created. - If an existing container is in draft (
READY_FOR_REVIEW) state, your assistant reuses it. - If no active container exists, your assistant proceeds to create a draft.
Stage 5: Create Review Submission Draft
Your assistant stages the creation of an empty ReviewSubmission container via review_submission_create_draft.
Creating a draft container does not submit your app to Apple. It simply prepares an empty envelope on Apple's servers into which version items can be placed.
Stage 6: Attach App Store Version to the Container
Your assistant links your editable version draft to the newly created submission container via review_submission_add_app_version. This designates the specific version, metadata, and binary that Apple review staff will evaluate.
Stage 7: Run Preflight Submission Verification
Before presenting the final approval card, your assistant calls review_submission_preflight. This compares your local submission composition against Apple's live server state, ensuring:
- All required container items are present.
- The attached build has not expired and maintains valid export compliance.
- No concurrent submissions are in progress on the platform.
Stage 8: Review in FlightDeck Desktop Approval Center
Because submitting to Apple App Review is a binding operational action, FlightDeck presents an interactive approval card in the desktop application:
Illustrative representation of the FlightDeck Approval Center sheet:
┌────────────────────────────────────────────────────────────────────────┐
│ FlightDeck Approval Center: Review Submission Dispatch │
├────────────────────────────────────────────────────────────────────────┤
│ App: Aurora Focus (ID: 6812899314) │
│ Version: 1.2.0 (Build 42, iOS) │
│ Platform: iOS │
│ Action: Submit App Review Draft to Apple │
│ Submission ID: sub-7f8e9d0a-1b2c │
│ │
│ Preflight Status: ALL 14 CRITERIA PASSED │
│ Payload Hash: sha256-a1b2c3d4e5f60718... │
│ │
│ [!] Notice: Clicking Approve will formally transmit this version to │
│ Apple App Review. Review queue times vary based on Apple volume. │
├────────────────────────────────────────────────────────────────────────┤
│ [ Reject ] [ Approve ] │
└────────────────────────────────────────────────────────────────────────┘
You inspect the exact app, version, build number, and preflight status, then click Approve to authorize dispatch.
Stage 9: Monitor Review Status Progression
Once approved, FlightDeck dispatches the submission to Apple's API. Your assistant queries the submission status to confirm Apple received the request.
Prompt: "Check the current submission status for version 1.2.0."
Your assistant reports the live status:
WAITING_FOR_REVIEW: Your app is queued for Apple review engineers (turnaround times vary based on submission queues; Apple reports most reviews complete within 24–48 hours).IN_REVIEW: An Apple reviewer is actively testing your binary on physical hardware.READY_FOR_SALE: Review passed and your app is approved for public distribution.REJECTED/UNRESOLVED_ISSUES: Reviewer flagged an issue; details appear in the App Store Connect Resolution Center.
What FlightDeck Does vs. What Remains External
| Capability | Handled via FlightDeck MCP | External / Web Portal Required |
|---|---|---|
| Inspect Version Drafts | Yes (automatic discovery) | No |
| Audit Readiness (14 Criteria) | Yes (release_readiness_check) |
No |
| Attach Processed Build | Yes (with Approval Center confirmation) | No |
| Create Submission Draft | Yes (review_submission_create_draft) |
No |
| Preflight Verification | Yes (review_submission_preflight) |
No |
| Dispatch to Apple App Review | Yes (review_submission_submit with approval) |
No |
| App Privacy Nutrition Labels | No (API does not support) | Yes (App Store Connect web portal) |
| Paid Apps Tax & Banking | No (API does not support) | Yes (App Store Connect Agreements) |
| Resolution Center Appeals | Guidance only via chat | Yes (App Store Connect web portal) |
Troubleshooting Submission Errors
"An active review submission already exists"
- Cause: Apple limits each platform to one open submission container at a time. A previous draft or in-review version is already registered.
- Resolution: Ask your assistant: "List active review submissions for iOS and report their current states." If a draft container exists, your assistant will attach items to it rather than creating a duplicate.
"Preflight check failed: Missing required screenshots"
- Cause: One or more supported display sizes (e.g., 6.7" iPhone or 12.9" iPad) lacks screenshots.
- Resolution: Upload at least one valid screenshot per supported display family before re-running preflight.
"Build is not eligible for submission"
- Cause: The binary is still in Apple's background processing queue (
PROCESSING) or lacks export compliance declarations. - Resolution: Wait for TestFlight processing to reach
VALID, confirm export compliance, and re-run preflight.
Related Documentation and Guides
- Pre-Flight App Store Submission Readiness Check
- Link TestFlight Build to App Store Release Version
- Diagnosing and Fixing App Store Rejections with an AI Agent
- Automating Multi-Language Localization and What's New
- Apple Developer: Review Submissions API Reference
- Apple Developer: App Store Review Guidelines