
My app is stuck in review for a long time – what should I do if it's taking too long?
Written by Laurens Dauchy
When your app is stuck in review for more than 7 days, there's usually a specific issue blocking approval. In my experience managing over 200 app releases, extended review times typically indicate compliance problems, technical issues, or queue backlogs that need proactive attention.
Here's what I've learned: most "stuck" apps have identifiable issues that can be resolved with the right approach. The key is systematic troubleshooting, clear communication with Apple, and understanding the common causes that trigger extended reviews. I'll show you exactly how to diagnose and resolve these situations.
What are the most common causes of extended review times?
Through analyzing hundreds of delayed submissions, I've identified the patterns that cause apps to get stuck in review. Understanding these helps you troubleshoot effectively.
Privacy and compliance issues
Apps with unclear privacy policies, missing data handling disclosures, or compliance violations get flagged for detailed review. This is the most common cause of extended delays I see.
Technical problems discovered during testing
Crashes, broken functionality, or security vulnerabilities found during review require fixes and resubmission. Each iteration restarts the review clock, extending total time.
Content and guideline violations
Apps with potentially inappropriate content, unclear age ratings, or features that might violate guidelines get escalated to senior reviewers, adding substantial time.
Payment and subscription issues
Problems with in-app purchase implementation, subscription management, or payment processing require additional verification and can extend reviews significantly.
How do I systematically troubleshoot a stuck app?
When an app gets stuck, I follow a systematic approach to identify and resolve the issue. Here's the process I use with teams:
Check for obvious issues first
- Verify all external links and resources are accessible
- Test your app on the latest iOS version and multiple devices
- Ensure in-app purchases and subscriptions function correctly
- Review your privacy policy for completeness and accuracy
- Check that your app doesn't crash on launch or during core functionality
Review your submission materials
- Ensure app descriptions match actual functionality
- Verify screenshots represent current app behavior
- Check that support and marketing URLs are live and relevant
- Confirm age ratings and content warnings are accurate
Short walkthrough
When should I contact Apple about a stuck app?
Contact Apple Developer Support when your app has been in review for more than 7 days without updates. Here's how to approach this effectively:
Timing considerations
Wait at least 7 days before contacting Apple, unless you have a critical business need. Most extended reviews resolve within this timeframe, and premature contact can slow down the process.
How to contact Apple effectively
- Use the "Contact Us" option in App Store Connect
- Provide your app's Apple ID and current review status
- Include any relevant context about your app's functionality
- Be specific about how long your app has been in review
- Ask for status updates or clarification on any issues
What information to include
Provide your app's name, Apple ID, submission date, and current status. Include any relevant business context, but avoid being pushy or demanding immediate action.
Prevent review delays before they happen
I use PTKD to catch privacy violations, security gaps, and compliance issues that commonly cause extended reviews. It spots problems that reviewers flag, saving weeks of back-and-forth.
Start free scanNo credit card. Results in minutes. Trusted by indie teams and enterprises.
What are the warning signs of a problematic submission?
Certain patterns in your submission can predict extended review times. Here are the red flags I watch for:
Complex app functionality
Apps with multiple integrations, payment systems, or user-generated content require more thorough testing and documentation review.
Unclear or missing documentation
Apps with vague descriptions, missing privacy policies, or unclear functionality get flagged for manual review by senior reviewers.
Previous rejection history
Apps from developers with previous rejections or guideline violations face additional scrutiny and longer review times.
Sensitive app categories
Financial, health, or social apps with user-generated content typically require more thorough review and longer processing times.
How do I prevent apps from getting stuck in review?
Proactive preparation is the best way to avoid extended review times. Here's my pre-submission checklist that measurably reduces delays:
Technical preparation
- Test all features thoroughly on multiple devices and iOS versions
- Ensure your app works offline if claimed
- Verify all links and external resources are accessible
- Test in-app purchases and subscription flows completely
- Check that your app doesn't crash on launch or during core functionality
Documentation and compliance
- Write clear, accurate app descriptions that match functionality
- Provide comprehensive privacy policy covering all data collection
- Include detailed app review notes for complex features
- Upload high-quality screenshots that represent actual app functionality
- Ensure support URL and marketing URL are live and relevant
Settings that matter for GDPR/PDPA/GR71
For teams in Europe (GDPR) and Southeast Asia (PDPA, GR71), compliance issues are a major cause of extended reviews. Proper preparation reduces these risks.
- Privacy policy completeness: Detail all data collection, processing purposes, and user rights
- Consent mechanisms: Clear opt-in for tracking and data processing
- Data retention policies: Specify how long data is kept and deletion procedures
- User rights implementation: Provide ways for users to access, correct, or delete their data
Helpful resources: Apple Review Guidelines, OWASP Mobile Security Testing Guide, and Google Play Data Safety for comparison.
What should I do while waiting for a stuck app?
Use the waiting time productively to prepare for potential issues and improve your app. Here's how I approach extended review periods:
Prepare for potential rejection
Use the time to prepare fixes for common rejection reasons. This way, if your app gets rejected, you can address issues quickly and resubmit faster.
Improve your app
Work on bug fixes, performance improvements, or new features that can be included in your next update. This maximizes the value of the waiting period.
Plan alternative strategies
Consider TestFlight distribution, alternative app stores, or web-based solutions as backup plans if App Store approval continues to be delayed.
How do I handle communication with Apple during delays?
Effective communication with Apple can help resolve stuck apps faster. Here's my approach to maintaining productive relationships:
Be professional and specific
Provide clear, factual information about your app and the delay. Avoid emotional language or demands, and focus on resolving the issue.
Provide helpful context
Include relevant business context, user impact, or technical details that might help Apple understand your app's purpose and functionality.
Follow up appropriately
Wait at least 3-5 days between follow-ups unless you have new information to provide. Excessive follow-ups can slow down the process.
Internal resources to help you prepare
- Standard App Store review timelines
- Expedited review options
- App Store Connect URL guidelines
- App security best practices
Key takeaways about apps stuck in review
Apps stuck in review for more than 7 days usually have identifiable issues that can be resolved with systematic troubleshooting. The most common causes are privacy violations, technical problems, and compliance issues.
Proactive preparation is the best prevention strategy. Thorough testing, clear documentation, and compliance preparation measurably reduce the likelihood of extended reviews and rejection.
For GDPR/PDPA/GR71 compliance, ensure your privacy and security practices are robust from the start. This prevents compliance-related delays and builds user trust while reducing review friction.

App Store review timelines
Read more
Expedited review options
Read more
App Store Connect guidelines
Read more
App security best practices
Read moreFAQ
How long is too long for App Store review?
Most apps should be reviewed within 7 days. If your app has been in review for more than 7 days without updates, contact Apple Developer Support for status updates.
Can I withdraw my app from review if it's taking too long?
Yes, you can withdraw your app from review through App Store Connect, but this restarts the review process when you resubmit. Only do this if you need to make significant changes.
Will contacting Apple slow down my review?
No, professional communication with Apple can actually help resolve issues faster. Just avoid excessive follow-ups and be specific about your concerns.
WRITTEN BY LAURENS DAUCHY - FOUNDER OF PTKD — 5 October, 2025