Overview: Verifying Submission Readiness Before Review
Before submitting your iOS application to Apple App Review, you can ask your AI coding assistant to run an automated, read-only pre-flight readiness audit through FlightDeck. Your assistant discovers your application record, inspects the active App Store version draft, and verifies the 14 structural criteria required by Apple's App Store Connect API.
Submitting an app with missing screenshots, an unattached binary, incomplete localized descriptions, broken support URLs, or missing demo credentials triggers immediate rejection, delaying your launch by days. Running an automated pre-flight audit catches mechanical submission blockers in seconds, distinguishes normal in-progress drafts from fatal blockers, and ensures your application package is structurally complete before review staff ever open it.
What Automated Preflight Verifies vs. What Remains External or Human-Governed:
- FlightDeck Automated Verification: Live App Store version draft status, attached binary processing state, export compliance declaration, screenshot presence across required display targets, localized metadata completeness, app title length, privacy policy URLs, customer support endpoints, and review contact details.
- External Web Portal Requirements: Apple does not expose the App Privacy Nutrition Labels questionnaire or Paid Applications tax and banking profiles through its public REST API. These declarations must be completed and confirmed directly within the App Store Connect web portal.
- Runtime & Editorial Realities: Passing pre-flight readiness does not guarantee Apple App Review approval. An automated readiness check verifies that your submission package satisfies Apple's structural API criteria; it cannot predict subjective editorial decisions, verify that your backend servers handle reviewer traffic, or replace testing on physical hardware.
The Primary Prompt: Run an Automated Submission Readiness Audit
Connect your AI coding assistant (such as Cursor, Claude Code, Xcode with MCP, or Antigravity) to FlightDeck and paste the following prompt:
Please run a complete pre-flight App Store submission readiness audit for my app using FlightDeck.
1. Dynamically resolve my app record and inspect the active App Store version draft.
2. Check all submission prerequisites: attached binary build, export compliance, required screenshot sets, localized descriptions, support and privacy URLs, and reviewer demo credentials.
3. Check for any unresolved issues or diagnostics from prior submissions.
4. Present a structured readiness report categorizing items into:
- Passed / Ready Items
- Fatal Blockers (preventing submission)
- Advisory Warnings
- Web Portal Prerequisites (actions required on apple.com)
- Recommended FlightDeck-assisted fixes
5. Do not modify any metadata or submit the app yet.
What Happens Behind the Prompt
When you run this prompt, your assistant handles the entire diagnostic inspection without requiring you to look up database IDs or construct API payloads:
Developer Prompt: "Audit my app for submission readiness"
│
▼
[1. Dynamic App & Version Discovery]
Assistant inspects app records and active version drafts
│
▼
[2. 14-Point Pre-Flight Audit Engine]
Assistant evaluates release readiness and build candidates
│
▼
[3. Historical Diagnostic Comparison]
Assistant checks prior submission diagnostics and rejection history
│
▼
[4. Structured Readiness Report in Chat]
Categorizes findings: Passed, Blockers, Warnings, Portal Actions
- Dynamic App and Version Discovery: The assistant identifies your app record and retrieves the current version draft in
PREPARE_FOR_SUBMISSIONstate. - 14-Point Pre-Flight Audit: FlightDeck queries live App Store Connect resources to evaluate your build, visual assets, metadata, and reviewer information against Apple's validation rules.
- Historical Error Diffing: If your app previously encountered submission errors or rejections, FlightDeck compares current draft state against historical diagnostic records to confirm that past issues are resolved.
- Structured Delivery: Your assistant formats the results into an actionable summary, separating items that are ready from blockers and web portal requirements.
What Your Assistant Delivers: The Readiness Report
Your assistant synthesizes the audit results into a structured summary:
App Store Submission Readiness Report
App: Aurora Focus (Bundle ID: com.aurorafocus.ios)
Version Draft: 1.2.0 (iOS) | Current Lifecycle State: NOT_READY_TO_SUBMIT
============================================================
1. PASSED / READY ITEMS (11 criteria)
------------------------------------------------------------
[x] Version State: Draft is open and editable (PREPARE_FOR_SUBMISSION)
[x] Binary Attached: Build 42 (VALID, uploaded 2 hours ago)
[x] Export Compliance: ITSAppUsesNonExemptEncryption set to false
[x] Build Expiration: Valid (88 days remaining in ingestion window)
[x] App Title: "Aurora Focus - Daily Routine" (28/30 characters)
[x] Primary Description: Complete (en-US, 1,420/4,000 characters)
[x] Support URL: https://aurorafocus.app/support (reachable HTTPS)
[x] Review Contact: Jane Doe (+1-555-0199, dev@aurorafocus.app)
[x] Age Rating: Declared (Ages 4+)
[x] iPhone Screenshots: 6.7" Super Retina XDR set present (4 images)
[x] iPad Screenshots: Universal app requirement satisfied (3 images)
============================================================
2. FATAL SUBMISSION BLOCKERS (1 item)
------------------------------------------------------------
[!] PRIVACY_POLICY_URL_MISSING
Detail: Privacy Policy URL is empty on the en-US storefront localization.
Apple Requirement: Guideline 5.1.1 mandates a valid, publicly accessible
HTTPS privacy policy URL for all apps submitted to the App Store.
Fix: Can be staged immediately via FlightDeck.
============================================================
3. ADVISORY WARNINGS (1 item)
------------------------------------------------------------
[*] KEYWORD_CHARACTER_BUDGET
Detail: Stored keywords use 98 of 100 available characters.
Note: Valid for submission, but near the maximum allowable length.
============================================================
4. WEB PORTAL PREREQUISITES (1 item)
------------------------------------------------------------
[?] APP_PRIVACY_LABELS_UNCONFIRMED
Detail: Data collection practices must be confirmed in App Store Connect.
Action Required: Log in to https://appstoreconnect.apple.com, select
Aurora Focus > App Privacy, and complete the questionnaire before submission.
============================================================
RECOMMENDED NEXT STEPS
------------------------------------------------------------
1. Tell me: "Update the privacy policy URL to https://aurorafocus.app/privacy"
2. Confirm your App Privacy questionnaire in the App Store Connect web portal.
3. Re-run this audit to confirm the overall state transitions to READY_TO_SUBMIT.
The 14 Audit Criteria Explained
FlightDeck checks 14 structural criteria across four key areas:
1. Build and Binary Integrity
- Version Draft State (
VERSION_STATE_EDITABLE): The release version must be in an editable status (PREPARE_FOR_SUBMISSION,DEVELOPER_REJECTED, orREJECTED). Versions that areWAITING_FOR_REVIEW,IN_REVIEW, orREADY_FOR_SALEcannot be modified or re-submitted. - Attached Binary (
BUILD_ATTACHED): An uploaded archive must be explicitly linked to the version draft. Having an.ipauploaded to TestFlight is not enough; it must be selected for the release. - Backend Processing (
BUILD_VALID): The attached build must have finished Apple's backend processing with statusVALID. Builds inPROCESSINGorFAILEDstate will block submission. - Build Ingestion Window (
BUILD_NOT_EXPIRED): Builds older than 90 days cannot be submitted for App Store release. - Export Compliance (
EXPORT_COMPLIANCE): The build must declare whether it uses encryption (ITSAppUsesNonExemptEncryption). If not declared inInfo.plist, an encryption questionnaire must be satisfied before submission.
2. Visual Storefront Assets
- Required Screenshot Coverage (
SCREENSHOTS_PRESENT): Apple requires at least one screenshot for each mandatory display target your application supports. - iPhone: A 6.7-inch Super Retina XDR display screenshot (1290 x 2796 pixels) is mandatory for modern iOS submissions.
- iPad: If your application bundle supports iPadOS, at least one 12.9-inch iPad Pro screenshot (2048 x 2732 pixels) is required.
- Myth: Apple does not require a minimum of 3 screenshots. Apple requires at least 1 screenshot per supported screen family (up to a maximum of 10).
3. Storefront Metadata and Legal Links
- App Title (
APP_NAME_CONFIGURED): Populated, within the 30-character limit, and free of prohibited terms. - Store Description (
LOCALIZATION_DESCRIPTION_PRESENT): Populated with non-placeholder text explaining what the app does. - Support URL (
LOCALIZATION_SUPPORT_URL_PRESENT): A valid, publicly reachable HTTPS endpoint where customers can contact support. - Privacy Policy URL (
PRIVACY_POLICY_URL): Required for all apps under Guideline 5.1.1. Must use HTTPS and be publicly reachable without authentication. - Age Rating (
AGE_RATING_DECLARED): The age rating questionnaire must be completed and assigned.
4. Reviewer Access and External Declarations
- Review Contact Details (
REVIEW_CONTACT_INFO): Contact first name, last name, phone number, and email for Apple review staff. - Demo Account Credentials (
REVIEW_DEMO_CREDENTIALS): If your app requires user authentication, functional credentials must be provided. Offline apps or apps without accounts mark demo credentials as not required. - App Privacy Labels (
APP_PRIVACY_LABELS): Must be answered directly in the App Store Connect web portal because Apple does not provide a REST API for privacy questionnaire responses.
Fixing Detected Blockers Through FlightDeck
When your audit uncovers metadata or build blockers, your AI assistant can resolve them through FlightDeck:
Fixing a Missing Privacy Policy URL
Please stage an update to set our privacy policy URL to https://aurorafocus.app/privacy for all active localizations.
Attaching the Latest Processed Build
Inspect available TestFlight builds for version 1.2.0 and stage attaching the latest valid build.
Adding Reviewer Demo Credentials
Stage review notes for version 1.2.0:
- Demo account username: reviewer@aurorafocus.app
- Demo password: ReviewPassword2026!
- Notes: "Tap 'Explore Demo' on the launch screen to bypass SMS verification."
Because updating metadata, attaching builds, and altering review credentials modify live App Store Connect resources, FlightDeck presents each staged change as an interactive card in the Desktop Approval Center. You review the exact fields and values, then click Approve to execute.
Verifying Pre-Flight Resolution
Once blockers are resolved and web portal questionnaires are confirmed, run a quick verification prompt:
Please re-run the pre-flight readiness audit for version 1.2.0. Confirm that the overall state is now READY_TO_SUBMIT and that all fatal blockers have been cleared.
When your assistant confirms that all 14 criteria pass and the lifecycle state reports READY_TO_SUBMIT, your application package is structurally complete and ready for submission drafting.
Common Pre-Flight Failure Modes
| Issue | Root Cause | Resolution |
|---|---|---|
BUILD_ATTACHED is blocked |
Archive uploaded to TestFlight but not linked to version draft. | Ask your assistant to list candidate builds and attach the valid build to the draft. |
EXPORT_COMPLIANCE missing |
Missing ITSAppUsesNonExemptEncryption key in Info.plist. |
Add the key to Info.plist for future builds; complete the encryption declaration on the current build in App Store Connect. |
PRIVACY_POLICY_URL missing |
Privacy policy URL omitted from app information or version localization. | Ask your assistant to stage the HTTPS privacy policy URL across active storefront localizations. |
SCREENSHOTS_PRESENT blocked |
Universal app missing iPad screenshots, or iPhone app missing 6.7" set. | Upload at least one screenshot for each mandatory display family supported by your app. |
APP_PRIVACY_LABELS action required |
Privacy questionnaire not completed in web portal. | Log in to App Store Connect, navigate to App Privacy, and publish your data collection declarations. |