Apple Guideline 2.1 (Performance): Fixing Crashes and Completeness Issues
Guideline 2.1 rejections mean Apple found performance problems with your app. This could be crashes, bugs, incomplete features, or placeholder content. These rejections are usually straightforward to fix once you identify the specific issue.
Scan your app against 180+ review rules
Get a detailed compliance report in under 5 minutes. Single scan $9, Pro $29/mo.
What Guideline 2.1 Covers
Guideline 2.1 - App Completeness requires that your app is "complete" at submission. This means: no crashes on supported devices, no obvious bugs that break core functionality, no placeholder content (lorem ipsum, coming soon pages), no beta or test labels, demo accounts work correctly if login is required, and all features described in metadata actually function.
Common Performance Rejection Triggers
App crashes on launch or during core functionality, features that do not work on the reviewer's device (typically latest iPhone with latest iOS), network-dependent features that fail without specific connectivity, demo credentials that do not work or are expired, onboarding flows that get stuck, and memory issues that cause the app to be killed by the system.
Prevention and Fixing
Test on the exact device and OS version reviewers use (latest iPhone, latest iOS). Provide working demo credentials in App Store Connect's review notes. Test your app after a clean install (not just an upgrade). Verify all network calls work without VPN or special configuration. Remove all placeholder content and "coming soon" sections. Run crash analytics and fix all known crash paths before submission.
Frequently Asked Questions
What device does Apple review on?
Apple reviews on the latest iPhone and iPad with the latest iOS version. Ensure your app works perfectly on these devices. Test on iPhone 15/16 Pro with the latest iOS release.
Do I need demo credentials for the reviewer?
If your app requires login, you must provide working demo credentials in App Store Connect's App Review Information section. Test these credentials before every submission.
My app works fine on my device but crashed during review. What happened?
Common causes: network-dependent features that fail on Apple's network, device-specific bugs, race conditions that only appear on faster hardware, or expired demo credentials. Test on a fresh device with a fresh install.
Related Resources
Check your iOS app against Apple's App Store Review Guidelines. Automated scanning covers all 5 guideline sections with specific fix recommendations.
App Rejected for CrashingFix app crash rejection from App Store or Google Play. Common crash causes during review, debugging strategies, and prevention tips.
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.
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