There is no secret escalate button for App Store review; escalation is a short ladder you climb only after a review is genuinely stuck. Apple reviews most submissions within 24 hours, so first confirm it is actually delayed and not held by your own settings. Then contact the App Review team about a review taking longer than expected, and if you have a real deadline, request an expedited review, which Apple grants sparingly. Apple Developer Support handles account and membership issues, not the review queue itself.
Short answer
Escalation means using the right channel once a review is truly delayed, not finding a hidden button. Apple states that most apps are reviewed within 24 hours, per its App Review page, so a submission sitting for several days is a reasonable point to act. First rule out your own settings, then contact the App Review team through the Contact page about a review taking longer than expected. For a genuine, time-sensitive deadline, request an expedited review, used sparingly. Reply in the Resolution Center for a specific rejection. Apple Developer Support is for account and membership issues, not review decisions.
First, is it actually delayed?
Before escalating, confirm the review is genuinely stuck, because most are not. Apple reviews about 90 percent of submissions within 24 hours, so a review that has run a day is normal, and even two days is not unusual during busier periods. Escalating a review that is still inside the normal window just adds noise and does not speed anything up.
Also rule out causes on your own side that look like a delay. Check whether your app is set to release manually rather than automatically, whether it is "Waiting for Review" versus "In Review," and whether a pending agreement or tax form is blocking the app. These are common reasons an app looks stuck when review is not actually the holdup, and they are things only you can fix.
The escalation ladder
Escalation is a sequence, and climbing it in order avoids wasted effort. You wait through the normal window, rule out your own settings, then contact the review team, and only request an expedite when there is a real deadline. The table below lays out the ladder.
| When | Action | Channel |
|---|---|---|
| First 24 to 48 hours | Wait, it is within the norm | None yet |
| Looks stuck | Rule out release option and agreements | App Store Connect |
| Past 2 to 3 days, no movement | Ask about a review taking too long | Contact the App Review Team |
| A genuine, dated deadline | Request an expedited review | Contact page, expedite form |
| Account or membership block | Apple Developer Support | Developer Support |
The key is to match the rung to the situation. Contacting the team about a slow review is appropriate after a couple of days; requesting an expedite is appropriate only when a genuine, dated event is at stake; and Apple Developer Support is for account problems, not for a review that is simply taking time.
Step 1: Contact the App Review team about a slow review
The first real escalation step is to contact the App Review team through Apple's Contact page and select the option about an app being in review longer than expected. This is the sanctioned way to ask Apple to look at a submission that has clearly exceeded the norm, and it goes to the team that can actually check on it.
Keep the message specific and calm. Give your app name and Apple ID, the submission and the date you submitted, and the current status, then ask directly about the delay. You are asking for a status check on a genuinely slow review, not demanding a faster decision, and a concise, well-identified message is what gets a useful reply rather than a generic one.
Step 2: Request an expedited review, and its limits
If a genuine deadline is approaching, you can request an expedited review, which asks Apple to move your submission ahead in the queue. You request it through the same Contact page, and Apple wants the specifics: the reason, the date, and why it is time-sensitive, such as a fix for a critical live issue or an app tied to a scheduled event.
Expedited review has real limits, and respecting them matters. Apple grants it at its discretion and sparingly, and it is meant for genuine urgency, not routine launches. Over-requesting expedites, or using one for a soft deadline, can lead Apple to deny future requests, so treat it as a limited favor you spend only when you truly need it. A strong, honest reason is what makes an expedite request work.
When to use Apple Developer Support
Apple Developer Support is a different channel with a different job. It handles enrollment, membership, account, and technical issues, so it is the right place when the blocker is your account rather than the review, for example a membership that has not renewed, an enrollment problem, or an account-level error. It is not the channel for asking why a specific app review is slow.
Sending the right problem to the right team saves days. If your app is stuck because of an account or agreement issue, Developer Support can resolve it; if it is stuck in the review queue, the App Review team through the Contact page is the correct destination. Confusing the two just adds a routing delay to an already frustrating wait.
What to include to get a fast, useful response
Whichever channel you use, the response quality tracks the information you give. A vague "my app is stuck" gets a slow, generic reply, while a specific, well-identified message gets a specific one. The checklist below covers the essentials.
| Item | Why it matters |
|---|---|
| App name and Apple ID | Locates your app |
| The submission and its date | Identifies the exact review |
| The current review status | Shows where it is stuck |
| A single, specific question | Gets a specific answer |
| Deadline and reason, if expediting | Justifies the request |
The theme is to make it effortless for Apple to find your app and understand your ask. Exact identifiers, the current status, and a single clear question do more than a long or emotional message, and if you are requesting an expedite, a concrete deadline and reason are what justify it.
Does resubmitting help or hurt?
For a delayed review, resubmitting usually hurts. Uploading a new build to replace the one in review starts the process over and sends you to the back of the queue, so an impatient resubmit typically lengthens the wait rather than shortening it. The review was likely to complete on its own, and you just reset it.
Resubmit only if you actually changed something that needs a new review, such as fixing a real defect. If the build is fine and simply slow, leave it in place and use the escalation channels instead. Replacing a submission that would have cleared is one of the most common ways developers accidentally extend their own delay.
What escalation cannot do
Be clear about the limits so you spend effort where it helps. Escalation can prompt a status check on a genuinely stuck review and, in real cases, expedite one; it cannot guarantee a review time, force a faster decision on a routine submission, or reverse a correct rejection because you are in a hurry. Apple does not offer a phone line for this either.
Knowing the limits keeps expectations realistic. If your app genuinely violates a guideline, escalation will not save it, and fixing the app is the path. If it is simply slow and past the norm, a specific contact message is the right move. Escalation is a tool for genuine delays, not a lever to jump the queue on demand.
Reduce the delays you can control
The delay you never have to escalate is the one you prevent. Many slow reviews and the rejections that follow trace back to avoidable issues, and a good share are security and privacy problems: an app requesting permissions it cannot justify, cleartext traffic where encryption is expected, or an embedded secret. Clearing these before you submit removes a common reason a review stalls or bounces.
A scanner like PTKD.com analyzes your .ipa and returns findings ordered by severity and mapped to OWASP MASVS, so you fix security and privacy issues before submission. To be clear about the boundary: PTKD cannot escalate a review, contact Apple, or expedite anything. It reduces the preventable problems that turn a normal review into a delayed or rejected one, which is the part of the timeline you actually control.
What to take away
- There is no secret escalate button; escalation is a ladder you climb only after a review is genuinely stuck.
- Most reviews finish within 24 hours, so confirm it is delayed and rule out your own settings before acting.
- Contact the App Review team about a review taking too long, and request an expedited review only for a genuine deadline.
- Expedited review is limited and discretionary; over-requesting can get future requests denied.
- Scan each build with PTKD.com before submitting, to prevent the delays and rejections you can control.
