The submitted build crashes or hides an important feature behind setup.
Submission checklist
App Store Review Checklist
Use this practical checklist to prepare your iOS app before App Store Review. It covers the build, metadata, screenshots, privacy details, review access and the common mistakes that create avoidable friction.
Review surface
- Build and flow readiness checks
- Metadata and screenshot consistency review
- Privacy and permission risk detection
- Review access preparation
Common mistakes before App Store Review
A submission can fail because the product experience and the App Store Connect package do not tell the same story. Review the fundamentals before you send the build.
Review credentials are missing, expired or do not show enough data.
Screenshots describe a feature that is incomplete or absent in the build.
Privacy details, permissions or tracking disclosures are inconsistent.
In-app purchases or subscriptions are not ready for review.
The app contains placeholder copy, test content or debug UI.
Use Klyre to check your app before submission
Klyre turns the checklist into a guided pre-review process. It helps inspect your build, metadata and submission assets before Apple Review sees them.
Build and flow readiness checks
Metadata and screenshot consistency review
Privacy and permission risk detection
Review access preparation
Potential rejection reasons with suggested fixes
A clearer path from pre-review to submission
Detailed preparation areas
Build checklist
The binary should be stable, current and representative of the experience described in App Store Connect.
- Use the release build you intend to submit.
- Run critical flows on real devices, not only simulators.
- Check launch, login, onboarding, purchase and account flows.
Metadata checklist
Apple reviews the product page as part of the submission package. Keep the listing accurate and complete.
- Align name, subtitle, description, screenshots and feature claims.
- Remove outdated screenshots and unsupported promises.
- Make support and privacy URLs reachable before review.
Privacy checklist
Privacy information should match the app behavior and the way permissions are presented to users.
- Review data collection details and privacy policy wording.
- Check permission prompts for clear context.
- Document account deletion and user data flows when required.
Review access checklist
If Apple cannot reach the core experience, the submission can stall or be rejected.
- Provide working credentials and enough demo data.
- Explain setup steps in review notes.
- Make gated or paid features reviewable.
App Store submission checklist
- 01
Test the app on real devices.
- 02
Make sure the app does not crash.
- 03
Provide review login credentials if needed.
- 04
Add complete metadata in App Store Connect.
- 05
Check screenshots and app previews.
- 06
Verify privacy information and policy links.
- 07
Confirm support URL and privacy policy are reachable.
- 08
Review in-app purchases and payment flows.
- 09
Check permission prompts and system dialogs.
- 10
Make sure the app matches the store listing.
- 11
Remove placeholder content and debug artifacts.
- 12
Add clear review notes for flows Apple cannot discover alone.
A clean pre-submission workflow
Prepare the release build you plan to send to Apple.
Collect App Store metadata, screenshots, privacy details and review notes.
Check build, metadata, privacy and review access risks.
Fix the highest-risk issues before opening the review request.
Submit through App Store Connect with a cleaner package.
Important limitation
Klyre does not replace App Store Review
Klyre helps you prepare a stronger submission, but the final review decision always belongs to Apple or Google. The analysis is guidance, not an approval guarantee.
FAQ
What should I check before App Store submission?
Check build stability, metadata, screenshots, privacy details, permission prompts, review credentials, support links and payment flows.
Can this checklist prevent every rejection?
No checklist can guarantee approval. It helps reduce avoidable risks, but Apple makes the final review decision.
Is this checklist useful for a small team?
Yes. It is designed for indie developers, studios and small agencies that need a clear pre-submission process.
How does Klyre improve the checklist process?
Klyre helps detect risks across the build, store metadata, privacy details and review access, then suggests fixes to review.
Does Klyre submit my app to Apple?
No. Klyre helps prepare your submission. You remain responsible for the final App Store Connect submission.
Prepare your App Store submission with Klyre
Turn your checklist into a focused pre-review before sending the build to Apple.