Apple Resolution Center: How to Reply to App Review

The Resolution Center doesn't exist under that name anymore. You reply to a rejection in your app's App Review section, with the Reply to App Review button. Write in English and give three things: what was blocking, what changed, and how to check it. The App Review Board only comes in after that reply, and only if you're sure your app follows the guideline Apple cited.

I wrote these replies for my own apps in 2026: Solys, my mini-game alarm clock, and TradaZen, my trading simulator. Here's where to reply today, what to write, when to attach a video, when to appeal, and what doesn't work. For the rejection reasons themselves, read why Apple rejects an app.

Where did the Resolution Center go?

The official help page, Reply to App Review messages, now talks about the App Review section. That's where you talk with Apple, attachments included, until you resubmit. The path:

1. In Apps, open your app.
2. At the top of the page, click the unresolved issues link, called View App Review Issues & Messages on another help page.
3. Under In Progress, click Resolve next to the submission.
4. Click Reply to App Review and write in the Reply field.
5. To attach a screenshot or a document, click Attach File, then Reply.

Only the Account Holder, Admin and App Manager roles can reply. The App Review page adds that you can track your submissions' status in App Store Connect or in its iPhone and iPad app.

Before you write: which message did you get?

The right reply depends on the message, not on your urge to defend yourself. Here's the grid I go through before opening the reply field.

What Apple says	What you do	New build
Information Needed	Answer the question	No
Bug or faulty screen	Fix it, then reply	Yes
Listing, links, screenshots	Fix the listing	No
App misunderstood	Explain, with proof	It depends
Ongoing disagreement	Appeal to the Board	No
Bug Fix Submissions offer	Accept by replying	No

Three details change everything:

• A metadata rejection doesn't need a new build. Apple's help says so: you fix it and resubmit the same build. That's often the case with a 2.3.10 rejection, when the offending mention is in the listing.
• An "Information Needed" isn't a real rejection. The reviewer is asking you a question. The guide on guideline 2.1 explains how that differs from an actual bug report.
• Bug Fix Submissions are an offer. If your app is already live and the message starts with "Bug Fix Submissions: The issues we've identified below are eligible to be resolved on your next update", you can request approval of the update by replying to the message. Don't resubmit the app at that point, or a new review starts. You fix the issue in the next version.

What to write: the four-block template

Apple published its advice on how to contact App Review. Do: be specific about what you're asking, and give information that helps them understand the app if you think it was misunderstood. Don't: use the reply field to appeal or request an expedited review, or ask about the status of other developers' apps.

My template fits in four blocks. Write in English, no adjectives. Replace everything in brackets, and only write what's true in the build you sent.

Hello App Review team,

Thank you for your review and for the details on
Guideline [number].

What you reported: [one sentence that restates
Apple's message, in your own words].

What changed in build [version (build)]:
- [Screen or element]: [what it does now]
- [Screen or element]: [what it does now]

How to verify:
1. [Starting point, e.g. fresh install]
2. [Action]
3. [Expected result]

We tested this flow on [devices and iOS versions].
[Attached: a short screen recording of the fixed flow.]

If anything else is unclear, please tell us which
screen or wording, and we will change it.

Best regards,
[Your name]

Each block has a job. The first proves you read the message. The second names the build, because the reviewer tests the binary, not your intentions. The third saves them time. The last leaves the door open without pleading.

Templates tailored to each guideline are in my dedicated guides, for example on guideline 3.1.2 or guideline 4.3. There's also a reply outline in my downloadable App Review notes template.

What I learned replying for Solys and TradaZen

Solys, guideline 2.1. The reviewer wanted a way to get past the game. My reply pointed to the blocking screen, the playable demo in onboarding, then the real cause: in compatibility mode on iPad, its obstacle became impossible to clear. It listed two numbered fixes, including a link to skip the demo after a failure, then the simulators tested, from the iPhone SE to the largest iPhone. It also described the alarm's emergency stop button, but only after I'd reread the code that triggers it. Don't write anything about your app that you haven't checked in the build.

TradaZen, guideline 5.6. In October 2026, Apple decided the app pushed users into unwanted in-app purchases, without pointing to anything specific. I looked for what could mislead people: an X at the top of the paywall opened a discounted offer instead of closing the screen. My reply admitted that in one sentence: it was my mistake. It then listed every change, screen by screen: the X replaced by a gift icon, no more offer reopening on its own, a promotional notification removed. It recalled what was still compliant: the billed price shown most prominently, purchase restoration, legal links. It ended by offering to change any screen still considered ambiguous. The new build went out with it.

Both replies follow the same logic: the real cause, the visible fix, the path to see it.

When to attach a video or a screenshot

Apple's help accepts screenshots and documents as attachments. A short video of the fixed screen is useful in three cases:

• the issue depends on a device or a condition, like an iPad in compatibility mode or a denied permission;
• the path to the screen is long, for example at the end of onboarding;
• the feature is hard to reproduce. The App Review page asks you to be ready to provide a demo video when a feature needs an environment that's hard to recreate or specific hardware.

For an app tied to an accessory, the help page on complete review requires a real video shot on an Apple device, not a screen recording. For paywall text or a renamed button, a screenshot is enough.

Requesting a call or an appointment

If writing isn't enough, Apple offers two options:

• A call with an Apple representative. You request it in the Reply to App Review window, after a first reply from App Review. Give your time zone and, if you want, your preferred language. Check your contact details in App Review Information first. Apple says these calls usually happen within three to five business days.
• A 30-minute video appointment with App Review, on Tuesday or Thursday, to talk about the guidelines. It's informational: it doesn't speed up or guarantee the review.

Appealing to the App Review Board

The appeal is the last step. According to the Appeal to the App Review Board page, it fits if your app was rejected but you think it follows the guidelines, or if you feel you were treated unfairly.

First, reply to the message in App Store Connect to clarify things. If that's not enough, fill out the Submit an appeal to App Review form. The rules:

• one appeal per rejected app, covering every guideline cited;
• cite the guideline and explain point by point how your app follows it;
• don't appeal if you've already fixed and resubmitted the app;
• don't appeal over a simple information request.

Apple gives two examples. Complete: "My app was rejected under 2.1 for incomplete information. The demo account and the steps to test the feature are in App Review Information, with screenshots showing it." Incomplete: "This app is important to my business and shouldn't have been rejected."

The Board replies in App Store Connect, and may ask for information or offer a call. Apple doesn't publish any timeline for appeals. Developers on Apple's forums report waits of more than two weeks. If the fix is simple, resubmitting a fixed build is often faster.

What works, what doesn't

Helps	Hurts
Restating Apple's reason	Pleading your case
Naming the fixed build	Promising a future fix
Giving the path to follow	Citing a competitor's app
Attaching proof	Appealing in Reply
One complete reply	Resubmitting without fixing

"My screen was already approved before" doesn't work either: every version goes through review again, sometimes with a different reviewer. The App Review Guidelines also warn that an app rejected several times for the same guideline takes longer to be reviewed. For review times, read App Store review time.

Get your reply checked before sending it

The Review Kit contains the actual messages my apps received, the fixes I sent, and Claude Code skills that draft your reply if Apple rejects you. For a human eye, book an hour with me: we read Apple's message and write the reply together. The full process is on the app rejected by Apple page.

Haven't submitted your app yet? Take the free diagnostic: it sends you my Apple anti-rejection checklist, so you don't have to write this reply at all.

Frequently asked questions

Where is the Resolution Center in App Store Connect?

It's now called the App Review section. Open your app, click the unresolved issues link at the top of the page, then Resolve next to the submission. The Reply to App Review button opens the reply field and lets you add attachments.

How long does Apple take to reply?

Apple doesn't publish a timeline for written replies. For reviews, Apple says at least 50% of submissions are reviewed in under 24 hours and 90% in under 48 hours. A call requested from App Review usually happens within three to five business days. No timeline is given for the App Review Board.

Can you reply to App Review in French?

Apple's help doesn't set a language for written replies. I write in English, in short sentences, to be understood the first time. For a call, Apple lets you give a preferred language, with no guarantee.

How many times can you appeal a rejection?

Once per rejected app. If the message cites several guidelines, your appeal has to cover all of them. Apple also asks you to reply in App Store Connect first, and not to appeal if you've already resubmitted a fixed build.

Should you resubmit a build before replying?

Yes if the issue is in the app: fix it, upload the build, then reply naming that build. No if the rejection is about metadata, like the listing or screenshots: you fix it in App Store Connect and resubmit the same build.