Getting rejected again after you already appealed feels like a dead end, but it is not. App Review has more than one step, and you can keep escalating, with the caveat that a second attempt only helps if you bring something new. Here is the ladder of options and how to make another appeal count rather than spinning in the Resolution Center.
Short answer
Yes, you can appeal again. App Review has an escalation ladder: reply in the Resolution Center to discuss the rejection, request a phone call, and escalate to the App Review Board, a panel of senior reviewers who review the case fresh. A second appeal works best when you have new information or have addressed the concern, since Apple advises against repeated appeals with nothing new. If the Board upholds the rejection, the practical next step is to change the build and resubmit, or to suggest a guideline change if you believe the rule itself is wrong.
What you should know
- You are not limited to one shot: the Resolution Center, a call, and the App Review Board are separate steps.
- The Board reviews fresh: senior reviewers not involved in your rejection look at the case anew.
- New information is the key: another appeal helps when you add something, not when you repeat yourself.
- Do not spam appeals: repeated identical appeals do not move the outcome and can slow things down.
- Appeal or resubmit: disagreeing with the interpretation is an appeal; a fixable issue is a resubmission.
What are the escalation paths after a rejection?
A few, in increasing weight. The table lists them and the rough response time.
| Path | What it is | Typical response |
|---|---|---|
| Reply in the Resolution Center | Discuss or clarify the issue with the reviewer | 24 to 72 hours |
| Request a phone call | Talk the rejection through with App Review | Scheduled |
| App Review Board appeal | A fresh review by senior reviewers | About 5 to 10 business days |
| Suggest a guideline change | Used when you think the rule itself is wrong | A separate process |
Most cases are resolved in the Resolution Center. The App Review Board is the real escalation, because it puts the case in front of reviewers who were not part of the original decision, which is what helps when the first reviewer made an error.
Can you appeal a second time?
Yes, and the App Review Board is how you do it properly. After a rejection, replying in the Resolution Center is your first conversation, and if that goes nowhere you escalate to the Board, which is itself a second look. You can come back again when something has changed, such as new evidence, a clarified explanation, or a fix you have made. What you should not do is file the same appeal repeatedly with no new content, because Apple advises against submitting multiple appeals when nothing has changed, and it does not improve your odds. So a second appeal is available; it just needs to carry something the first one did not. A practical test is whether you can name what changed in one sentence; if you cannot, you are probably about to repeat yourself, and a resubmission or a clearer argument is the better move.
How do you make a second appeal count?
Give the Board a reason to decide differently. Be specific about which guideline you were rejected under and why you believe your app complies, point to the exact screen or behavior the reviewer may have missed, and include any new information, a demo account, a video, or a clarifying note. Keep the tone calm and factual rather than frustrated, since the people reading it were not involved in the first decision and respond to evidence, not pressure. If you have changed the app in response to the feedback, say exactly what changed. A focused, evidence-led second appeal is far more likely to land than a longer, angrier version of the first. It also helps to answer any question the reviewer or the Board already asked before you escalate again, since an unanswered request for information is a common reason a case stalls.
When should you stop appealing and change the build instead?
When the issue is a real, fixable problem rather than a disagreement about interpretation. Appeals are for cases where you believe the rejection misread your app or applied a guideline incorrectly. If the rejection points at something concrete you can fix, a crash, a missing purpose string, a policy your app genuinely does not meet, the faster path is to fix it and resubmit, not to argue. And if the Board upholds the rejection and you still believe the guideline itself is wrong, the channel for that is to suggest a guideline change, which is a separate process from appealing your specific app.
What to watch out for
The first trap is assuming more appeals carry more weight; they do not, and spamming the Resolution Center can slow your case. The second is confusing an appeal with a resubmission, since a guideline disagreement and a fixable bug call for different responses. Appeals are about how a guideline was applied, which is separate from the technical state of your build, so they sit apart from a pre-submission scan; if the rejection was a binary issue, a scan such as PTKD.com (https://ptkd.com) reads the compiled IPA against OWASP MASVS to confirm the fix before you resubmit, rather than appealing something you can simply correct. Match the response to the cause.
What to take away
- Yes, you can appeal again: reply in the Resolution Center, request a call, and escalate to the App Review Board.
- The Board is a fresh review by senior reviewers, which helps when the first reviewer made an error.
- A second appeal only helps with new information, so add evidence and avoid repeating the same argument.
- If the rejection is a fixable issue, fix and resubmit instead of appealing, and confirm a binary fix with a pre-submission scan such as PTKD.com.
