Upload your IPA. Get an instant report detecting privacy manifest issues, debug builds, wrong provisioning profiles, permission problems, and every other common App Store rejection cause.
Eight automated checks covering every common technical rejection cause on the App Store.
Debug build detection
Identifies whether your IPA was built for development or distribution. Development builds are rejected by App Store Connect before review begins.
Provisioning profile type
Extracts the embedded.mobileprovision from your IPA and confirms it is a Distribution profile, not a Development or Ad Hoc profile.
Privacy manifest (PrivacyInfo.xcprivacy)
Verifies the presence of the required PrivacyInfo.xcprivacy file. Missing privacy manifests are a rejection cause for all apps built with iOS 17 SDK or later.
Required Reason APIs
Scans for usage of APIs that require a declared reason in the privacy manifest: UserDefaults, file timestamps, disk space, system boot time, and others.
Permissions (Info.plist usage descriptions)
Lists every permission string in Info.plist. Flags any permissions without a usage description string — required by Apple for all permission requests.
App Transport Security
Checks for ATS exceptions that allow cleartext HTTP. Production apps should not disable ATS without justification declared in App Store Connect.
Xcode SDK version indicator
Extracts build metadata to indicate the Xcode SDK used. Apple periodically enforces minimum Xcode version requirements for new submissions.
Minimum iOS deployment target
Checks the minimum supported iOS version. Flags targets below the recommended threshold for the current year's device distribution.
Upload your IPA
Drag and drop or select your IPA file. Files are analysed in an isolated environment. Only metadata and manifest data is extracted — no source code, user data, or binary logic is read.
Instant analysis
The checker extracts your provisioning profile, Info.plist, privacy manifest, and binary metadata. Results are ready in under 30 seconds.
Read your report
Each check shows pass, warning, or fail. Every issue includes a plain-English explanation and the exact fix — no guessing what the error means.
Fix and verify
Rebuild, re-export from Xcode using the correct distribution configuration, and run the checker again before submitting to App Store Connect.
Since Apple made PrivacyInfo.xcprivacy mandatory for all apps built with the iOS 17 SDK, missing or incomplete privacy manifests have become the leading cause of iOS app rejections. The iOS App Checker verifies your manifest and flags every required reason API that is not declared.
Read the iOS Privacy Manifest Guide →App Store Connect pre-screens every submission
Automated checks run before a human reviewer ever sees your app. A debug build or wrong provisioning profile is caught and rejected instantly.
Review cycles are expensive
An iOS review cycle is typically 24–72 hours. A technical rejection means restarting that clock. One check before submission prevents this entirely.
Xcode can export the wrong configuration
It is easy to accidentally export an archive with a Development profile instead of Distribution. The checker catches this immediately.
Privacy manifest requirements change
Apple adds new Required Reason APIs periodically. The checker always reflects the current list, not last year's requirements.
No account. No credit card. Upload your IPA and get your App Store readiness report in under 30 seconds.
