1. Reference
The guideline number and one line acknowledging the finding. No defense yet.
How Resolution Center works
Every app version has a message thread in App Store Connect. Apple writes the rejection there; you reply there, with text and attachments (screenshots, screen recordings, PDFs). If you changed the binary, upload a new build with a higher build number and submit the version again; your reply then explains the build. If only metadata changed, edit it, save, and reply that it is updated; the same build is reviewed again. Replies are read by the review team, not always by the same reviewer, so each reply should stand on its own.
Anatomy of a reply that gets approved
2. What changed
Numbered list, one line each, past tense. "Added Sign in with Apple to the login screen."
3. Where to find it
Exact path in the app for each item: "Settings, Account, Delete account".
4. Build and account
New build number and the demo credentials, repeated even if unchanged.
5. Evidence
A 30 to 60 second screen recording or two screenshots attached, named clearly.
6. Offer
One sentence offering a call or more information. Then stop writing.
Template A: fixed and resubmitted
Reply after changing the app (new build)
Thank you for the review and for pointing out the issue under Guideline [number]. We have addressed it in build [build number], now submitted: 1. [Change, e.g. Added an in-app account deletion option] - [location, e.g. Settings, Account, Delete account]. 2. [Change] - [location]. 3. [Change] - [location]. Demo account: [email] / [password] (pre-confirmed, sample data included). A screen recording showing items 1 to 3 is attached. Please let us know if anything else is needed. Thank you.
I am very happy I bought this app! Extremely easy and great documentation. Was in contact with the customer service, they replied very quickly and very friendly. They solved my question within a day. 10/10 would recommend.
Template B: the reviewer missed something (no change needed)
Reply when the feature exists and the build stays the same
Thank you for the review. We believe the functionality referenced under Guideline [number] is already present in build [build number], and we would like to point to where it can be found: - [Feature]: [exact path, e.g. tap the profile icon, then Settings, then Delete account]. - [Feature]: [exact path]. The attached screen recording (00:00 to 00:45) shows the steps on an iPhone with the demo account [email] / [password]. If the behavior differs on your device, we would appreciate a screenshot or the device and iOS version so we can reproduce it. We are also glad to schedule a call. Thank you for your help.
Template C: information or demo account requested
Reply to a 2.1 information request
Thank you for your message. Here is the requested information. What the app does: [App name] lets [who] [do what]. The web version is at [URL]; this iOS app adds [push notifications, Face ID lock, offline screen, native sharing]. Demo account: [email] / [password]. The account is pre-confirmed, has no two-factor codes and contains sample [projects/orders/chats]. Second role, if needed: [email] / [password]. How to reach the main features: - [Feature]: [path] - [Feature]: [path] [Anything unusual: hardware, region, first load takes a few seconds while the backend starts.] Contact during review: [name, phone, email]. Thank you.
Template D: metadata-only fix
Reply after updating screenshots, name or description (same build)
Thank you for the review. We have updated the App Store metadata as requested under Guideline [2.3.x]: 1. Replaced all screenshots with captures from the iOS app (iPhone [size] and iPad [size]). 2. Removed references to [other platforms / beta / third-party names] from the description and subtitle. 3. Changed the app name to [new name] to match the name shown on the device. No changes were made to the binary; build [build number] remains the submitted build. Please let us know if anything else should be adjusted. Thank you.
What not to write
- Apologies longer than one line, or explanations of how hard you worked.
- Promises about future updates instead of changes in this build.
- Technical details about the framework or the AI tool that built the app.
- A new bundle ID or a second app record to "start fresh"; see repeated rejections.
Attachments and timing
| Situation | Attach | When to send |
|---|---|---|
| Fixed in a new build | Screen recording of each change, 30 to 60 seconds | Right after the new build finishes processing; submit the version in the same session. |
| Reviewer missed a feature | Recording with timestamps, device and iOS version | Same day. Do not upload a new build unless you also changed something. |
| Demo account requested | Nothing required; a short walkthrough video helps | Within hours. The review is paused until you answer. |
| IP or rights question | License receipts, registration, written permission as PDF or screenshots | Before replying; gather documents first, then answer once. |
Frequently asked questions
How long should a reply be?
Under 200 words in most cases. Numbered items with locations are read; paragraphs are skimmed.
Do I reply before or after uploading the new build?
Upload first, wait until the build has processed, submit the version, then reply with the build number. A reply that references a build Apple cannot see yet causes a round trip.
What if I disagree with the rejection?
Use Template B with evidence first. If the answer still disagrees, ask for a call and then consider an appeal to the App Review Board; the repeated-rejections guide explains when each is worth it.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageCloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.