Restate the issue without arguing about intent
Describe what the reviewer saw and where it occurs. If access failed, verify the review account and backend availability. If functionality was misunderstood, provide short navigation steps and relevant screenshots. Saying that many other apps behave the same way does not explain your implementation or establish compliance. Keep the response centered on the cited issue and the submitted build.
Attach evidence for the proposed resolution
For a fix, identify the new build and what changed. For a clarification, give a reproducible path and the information the reviewer needs. Do not claim a payment or permission flow works because it compiled; check the appropriate environment and record the result. Avoid sharing customer credentials or confidential personal data in attachments. Use the review-information fields and approved communication channel.
Choose clarification, resubmission or appeal deliberately
Apple allows correspondence and attachments through App Review messages. Use the current process for your case and preserve the exchange. If a substantive disagreement remains, review the formal appeal route rather than repeatedly uploading unchanged builds. No response template guarantees approval. Keep the team’s release plan flexible until the submitted version actually receives a decision.
Working example
Reply outline: ‘You identified issue X under guideline Y. In build Z we changed the behavior at this screen. To verify it, sign in using the review account and follow steps one through three. The attached capture shows the resulting state.’ Replace every placeholder with confirmed facts. If no fix was made, explain the implementation rather than presenting an imaginary change.
Your next steps
- Use the actual cited guideline and build.
- Validate review access and backend availability.
- Provide short reproduction steps and safe evidence.
- Claim approval only after the console confirms it.
Official sources
Sources checked October 2, 2026. Review the current provider documentation before acting on requirements.
Turn the next test into something useful.
Publish a focused brief on RateMyApp. Credits fund approved private reports; public store reviews are voluntary and unrewarded.
List your app for feedback