Submit for Review

Process Overview

1. Attach a build, fill in metadata, submit for review.
2. Enter Waiting For Review, queued.
3. In Review, you may receive messages or a call.
4. Result: Ready for Sale (approved) or Rejected.

Submit → Waiting for Review → In Review → Approved (Ready for Sale)
                                  │
                                  └→ Rejected → Fix → Resubmit

Review Timeline

• Usually 1-3 business days; longer during holidays or peaks.
• External TestFlight testing also needs review, usually faster.
• Special cases (new accounts, sensitive categories) may take longer.

Materials Checklist

• Test account/password and test steps
• VPN/special-environment instructions if needed
• Paid/subscription path; IAP purchasable
• Third-party content/copyright proof (if any)
• Review notes: feature highlights, test path, caveats

Handling Rejections

1. Read the reason in Resolution Center.
2. Fix accordingly (code / metadata / privacy / IAP, etc.).
3. Reply in Resolution Center explaining what changed, then resubmit.
4. If it’s a mistaken rejection, provide a reproduction video/log.
5. For repeated rejections, consider a phone call or formal appeal.

Common Rejection Handling

Self-Check List

• Correct build attached and metadata complete
• Test accounts and steps ready
• Review notes written
• Timeline understood and release window planned
• A rejection handling plan prepared

FAQ

• How long does Waiting For Review take? No fixed duration; peaks can be long. Be patient — don’t repeatedly “update” builds.
• Can I resubmit immediately after rejection? Fix thoroughly and self-test first to avoid the same rejection.
• How do I contact reviewers? Message via Resolution Center or request a phone call (supported in some cases).