If my app is rejected, will the next review take as long as the first one or is it quicker?

Resubmissions usually review faster than first submissions, provided you fix the issue clearly and document it in Review Notes. In my experience, targeted fixes often pass within 24–48 hours.

The exception: if your fix introduces new IAPs, permissions, or policy‑sensitive changes, expect a full pass that can take longer. Treat those like a mini‑launch.

Why resubmissions are often quicker

• Known context and metadata; reviewers focus on the fix.
• Clear Review Notes reduce clarification loops.
• Stable links and assets already vetted.

Short walkthrough

How to write effective resubmission notes

• Reference the rejection reason and guideline numbers.
• Explain the change and how to verify it quickly.
• Provide credentials or test data if relevant.

Checklist to avoid repeat rejections

• Reproduce the issue; add test coverage if possible.
• Retest purchases and permissions on a clean device.
• Verify support/privacy URLs and content from mobile.

Settings that matter for GDPR/PDPA/GR71

• Consent aligned with actual tracking behavior.
• Clear data rights instructions and reachable contact.
• Third‑party SDK disclosure updated if changed.

References: Apple Review Guidelines, OWASP MSTG, Google Play Data safety.

FAQ

How soon should I resubmit after a rejection?

As soon as the fix is verified. Faster, high‑quality resubmissions tend to move quickly.

Will contacting Apple help?

If the rejection is unclear, ask for clarification in Resolution Center before resubmitting.

Does expedited review apply after rejection?

Only for critical fixes (security, crashes, paid access). Provide strong evidence.

Expedited review guide

Read more

Review timelines

Read more

Approval vs rejection alerts

Read more

Pending Developer Release

Read more