App Rejected for Crashing: Find and Fix the Problem
A crash during app review is an automatic rejection. The frustrating part: your app might work perfectly on your devices but crash on the reviewer's setup. Here is how to diagnose review-specific crashes and prevent them.
Scan your app against 180+ review rules
Get a detailed compliance report in under 5 minutes. Single scan $9, Pro $29/mo.
Why Apps Crash During Review
Apps crash during review for reasons that do not always show up in your testing: reviewers use the latest devices with the latest OS (your test devices might be older), network conditions differ (Apple reviews from specific locations), test/demo credentials expire between submission and review, server-side features may be down during the review window, and race conditions that only appear on faster hardware.
Diagnosing the Crash
Apple sometimes provides crash logs in the Resolution Center. If available, these are your best diagnostic tool. If not, reproduce the issue by: testing on the exact device and OS version the reviewer used (latest iPhone, latest iOS), using fresh install (not upgrade), testing with the demo credentials you provided, checking your server logs for errors during the review timeframe, and testing on different network conditions.
Preventing Review Crashes
Add comprehensive crash reporting (Crashlytics, Sentry) so you see crashes in real-time. Test on the latest hardware and OS before every submission. Verify demo credentials work at submission time, not just when you created them. Ensure your backend services are stable during the review window. Handle all network errors gracefully. Test edge cases like expired tokens, empty states, and offline mode.
Frequently Asked Questions
Can I see what the reviewer saw when my app crashed?
Apple sometimes attaches crash logs or screenshots in the Resolution Center. Google provides less diagnostic information. Always check the Resolution Center for reviewer-provided details.
My app works fine on my phone. Why did it crash for the reviewer?
Common reasons: different device model, different OS version, different network environment, expired credentials, or server issues during review. Test on the latest hardware with fresh credentials.
How do I prevent crashes I cannot reproduce?
Use crash reporting tools that capture crashes in production. Test on the exact device/OS combination reviewers use. Implement comprehensive error handling for all network calls and edge cases.
Related Resources
Fix Apple Guideline 2.1 performance rejection. Common performance issues, crash prevention, and completeness requirements for App Store approval.
App Store Rejection ReasonsComplete list of App Store and Google Play rejection reasons. Learn why apps get rejected and how to prevent each rejection type.
How to Fix App Store RejectionStep-by-step guide to fixing any app store rejection. Diagnose the problem, implement the fix, and verify compliance before resubmitting.
Stop Guessing. Start Scanning.
Join developers who pass app store review on their first try.
Start Free ScanSingle scan $9 · Pro $29/mo · Team $79/mo