App Store review, submission, and ASO guide

    Most App Store rejections come from a small set of recurring issues: missing privacy URLs, broken sign-in flows, deprecated APIs, or metadata that trips Apple's reviewers. This cluster covers the submission, review, and store-optimisation questions PTKD users ask most often — including expedited review, status meanings, and what to do when your app is stuck.

    Pages are grouped below by submission stage. Security-related App Store rejections are covered in the Android and iOS clusters.

    36 guides in this cluster

    The App Store review funnel, end to end

    A submission flows through five status transitions before it's live. Most teams only know the first and the last; the middle three are where the surprises hide:

    1. Prepare for Submission. Your binary is uploaded but you haven't hit Submit yet. Metadata and screenshots can still change.
    2. Waiting for Review. Apple's queue. Typically 24–48 hours, longer near launches and major iOS releases. The status doesn't mean anyone is reading your app yet.
    3. In Review. A human reviewer is examining your app. Usually a few hours; rare for it to exceed 24 hours unless they hit a blocker.
    4. Pending Developer Release. Approved. Waiting for you to manually release. This can sit indefinitely.
    5. Ready for Sale. Live on the App Store in the territories you selected.

    Rejection (Metadata Rejected, Binary Rejected) can happen at the In Review stage; both let you respond, fix, and resubmit without a full re-queue.

    The six rejections you'll hit at least once

    1. Guideline 5.1.1 — privacy policy URL missing or unreachable. Always supply a public, browseable HTTPS URL — not a file in the bundle, not a localhost link.
    2. Guideline 2.3.3 — screenshots don't match the app. Reviewers reject stylised mockups that don't show the actual UI. Capture real screens from the build you're submitting.
    3. Guideline 4.0 — uses non-public API. A dependency called a private selector or read an undocumented Info.plist key. PTKD's scanner flags these before submission.
    4. Guideline 2.1 — broken sign-in for review account. Provide a real test account that works. Reviewers don't debug your auth flow.
    5. Guideline 4.2 — minimum functionality. Web-view-only apps and re-skinned templates get rejected here. Add native value.
    6. Guideline 5.1.2 — third-party SDK data sharing not disclosed. Your privacy nutrition label must match every SDK's actual data collection. PTKD's SDK report enumerates what each one collects.

    When and how to request expedited review

    Apple grants expedited review for two valid reasons: a critical bug already-live in production that's harming users, or a time-sensitive event your app supports (launch day for a coordinated marketing push, seasonal content). Marketing pressure and self-inflicted deadlines aren't valid reasons.

    One expedited request per app per year is the unwritten limit before Apple stops granting them. Spend it on the critical-bug case and not on a launch you could have planned around the queue.

    Where to start

    If you only have time for a few pages from this cluster, these are the most-asked guides.

    1. 01
      How long does Apple App Store review typically take for a new app submission?

      The actual current review timing, with the factors that change it.

    2. 02
    3. 03
      Pending Developer Release: What the Status Means

      What the status means and how to use it for coordinated launches.

    4. 04
      My app is stuck in review for a long time – what should I do if it's taking too long?

      What to do when In Review doesn't move for more than 48 hours.

    All guides in this cluster

    Overview

    App Store Connect

    Store optimisation

    Submission

    Frequently asked questions

    How long does App Store review actually take in 2026?
    The median for first submissions is around 24 hours; updates median around 18 hours. Both numbers grow during the days before iOS major releases, around Apple keynotes, and through the December holiday window. Expedited reviews land in 4–12 hours when approved.
    Can I update an app already live without going through review again?
    No — every binary update goes through review. Metadata-only updates (description, screenshots, keywords) go through a lighter review that's usually same-day. In-app content delivered via your backend (CMS-driven copy, server-rendered screens) doesn't need review at all.
    Does Apple work weekends?
    Apple's review team operates seven days a week with reduced staffing on weekends and US holidays. Don't submit late Friday expecting Monday turnaround; submit Tuesday-Thursday for the most predictable timeline.
    What's the difference between Waiting for Review and In Review?
    Waiting for Review = your app is in Apple's queue, no human has looked yet. In Review = a reviewer has picked it up and is actively evaluating. The transition usually happens within 24 hours; if Waiting for Review sits longer than 72 hours without movement, that's when to contact Apple Developer Support.
    Can I withdraw a submission after I've sent it for review?
    Yes. App Store Connect has a Remove This Version option that works at every stage before Ready for Sale. Use it when you spot a bug after submission rather than waiting for Apple to reject; it's faster than the appeal-and-resubmit loop.