App Store Submission Checklist to Avoid Rejections

A rejection can delay your launch or update by days, so submitting cleanly the first time is worth the preparation. This app store submission checklist walks through the review-guideline, metadata, and technical checks that prevent the most common rejections, so your app clears review smoothly in 2026. It complements your ASO work: getting live without delay lets your optimized listing start earning installs sooner.

For updates specifically, see our guide to the iOS app release checklist; for launch, the mobile app launch checklist.

Why a submission checklist matters

Before the specific items, it is worth understanding why a deliberate pre-submission check pays off. App review exists to protect users and uphold store standards, and reviewers reject apps that fail on functionality, metadata accuracy, privacy, or guideline compliance. A rejection is not just a setback — it costs you the review turnaround time again, delaying your launch or update and any momentum tied to it. Most rejections, however, stem from a handful of avoidable causes, and a systematic app submission checklist catches them before you submit rather than after a reviewer does. Working through the checks below turns submission from a gamble into a routine, dramatically improving your odds of a first-pass approval. Given how much a delayed launch can cost in lost momentum, the modest time spent on a pre-submission review is one of the highest-return habits in the whole release process.

1. Review-guideline compliance

Start by checking your app against the store's review guidelines, since violations are a frequent rejection cause. Confirm your app does what it claims and provides genuine value, since thin or purely promotional apps are rejected. Ensure it does not duplicate existing functionality without adding value, does not use private APIs or prohibited practices, and handles any sensitive content, user-generated content, or regulated categories according to the rules. If your app touches areas like health, finance, or children's content, verify you meet the specific requirements for those. Reviewing the guidelines relevant to your app's category before submitting, rather than assuming, catches compliance issues early. This item is foundational because a guideline violation can block an otherwise polished app, and reviewers apply these rules consistently.

2. Complete and accurate metadata

Check that your metadata is complete, accurate, and non-misleading, since metadata problems are a top rejection cause. Ensure every required field is filled, your description accurately reflects what the app does (no promises the app does not keep), and your screenshots show the actual app rather than mockups or unreleased features. Verify there is no placeholder text, no broken links (support URL, privacy policy URL), and no references to other platforms or to beta status. Confirm your keywords and description do not make misleading claims. Accurate metadata is both a submission requirement and good ASO — it must persuade honestly. This item overlaps with your optimization work, but here the focus is compliance: metadata that is complete, truthful, and free of the placeholders and broken links that trigger rejections.

3. Functionality and stability

Test your app thoroughly for stability and completeness, because crashes and broken functionality are among the most common and clear-cut rejection reasons. Confirm the app does not crash on launch or during normal use, that all advertised features actually work, and that there is no placeholder or incomplete content. If parts of your app are behind a login or paywall, provide reviewers with working demo credentials or access so they can evaluate everything. Testing across the devices and OS versions you support catches issues a single test device might miss. This functionality check is where thorough pre-submission testing prevents the frustrating, avoidable rejections that come from a reviewer hitting a crash or a dead feature you could have caught.

4. Privacy and permissions

Check your privacy and permissions carefully, since these are increasingly scrutinized and a frequent rejection cause. Confirm your privacy policy is present, accurate, and linked correctly. Ensure your privacy disclosures — what data you collect and how you use it — are complete and truthful, matching your app's actual behavior. Verify that every permission your app requests (location, contacts, camera, notifications) is genuinely needed and clearly justified to the user, since requesting permissions without evident purpose is rejected. If you use third-party SDKs, account for the data they handle in your disclosures. Privacy compliance is both a rejection-avoidance item and a trust matter, so getting it right protects both your approval and your users. This area has grown more important over time, so treat it as a core checklist item rather than an afterthought.

5. Ratings, content, and technical requirements

Finish with the remaining compliance items. Confirm you have set an accurate content/age rating reflecting your app's actual content, since a mismatch causes rejection. Check technical requirements: your build targets a current SDK, your screenshots meet the required sizes and show real content, your app icon is present and correct, and your build is properly signed and configured. Ensure any in-app purchases or subscriptions are correctly set up, described, and use the store's billing as required. These items are less about judgment and more about correctness, but they cause real rejections when overlooked, so a final pass through the technical and rating requirements ensures nothing procedural blocks your otherwise-ready app. This ios app submission checklist step is the last gate before you submit with confidence.

A worked example

Consider a team preparing to submit an app who use this checklist to avoid the rejections that had delayed them before. On guidelines, they confirm their app provides genuine value and complies with the rules for their category. On metadata, they catch and fix a broken support link and remove a screenshot showing an unreleased feature. On functionality, thorough testing surfaces a crash on an older OS version, which they fix, and they add demo credentials for their gated features. On privacy, they complete their disclosures to match the app's actual data use and remove a permission request they could not justify. On technical items, they correct a mismatched content rating and a wrong screenshot size. They submit — and pass review on the first attempt, launching on schedule. Compared to their previous submit-and-get-rejected cycle, the checklist saved them days and let their optimized listing start earning installs immediately. That is the value of submitting cleanly.

Common mistakes

The recurring mistakes are submitting without reviewing the guidelines, leaving broken links or placeholder content in metadata, failing to test for crashes across devices, omitting or mismatching privacy disclosures, requesting unjustified permissions, and setting an inaccurate content rating. A systematic pre-submission pass catches these before a reviewer does, avoiding the delay of a rejection.

Let AppsLift get your optimized listing live and ranking

A clean submission gets your app live; strong ASO makes it grow — and building rankings for your app is exactly what AppsLift does. Since 2012 we have pushed 400+ iOS and Android apps to the top of store search, turning organic search into their cheapest install channel once they are live.

Start with a free AppsLift audit: paste your app link, pick your markets, and see your real keyword positions plus the install value of reaching the Top 3. When you want your rankings built for you after launch, talk to our team. Next, read our guide to the iOS app release checklist.