All posts

App Store rejection: common issues and how to check first

· 7 min read

Your first iOS app is done and you press Submit for Review. A rejection is common, and it is rarely a surprise once you read the message. Apple lists the issues it sees most often. This post goes through that list, what the main guidelines ask in plain words, a check to run before you submit, and what to do if you are rejected anyway.

I checked Apple's pages in November 2026. Apple changes these pages, so check them again before you rely on them. The main source is Apple's App Review page (the old address, developer.apple.com/app-store/review, redirects there). The rules themselves are in the App Review Guidelines.

What Apple lists as common issues

Apple has a section called Avoiding common issues. It says that "over 40% of unresolved issues are related to guideline 2.1: App Completeness". Apple's list is:

  • Crashes and bugs
  • Broken links
  • Placeholder content
  • Incomplete information
  • Privacy policy issues
  • Unclear data access requests
  • Inaccurate screenshots
  • Substandard user interface
  • Web clippings, content aggregators, or a collection of links
  • Repeated submission of similar apps
  • Copycats
  • Misleading users
  • Not enough lasting value
  • Submitted by incorrect entity

For a small first app, I would worry about the first seven and the one about lasting value. The rest matter, but they are less likely to catch a solo maker who built something honest.

What the main guidelines ask

2.1 App Completeness

Guideline 2.1 says submissions should be final versions with all necessary metadata and fully functional URLs. Placeholder text, empty websites and other temporary content should be scrubbed. It also says to make sure your app has been "tested on-device for bugs and stability" before you submit. If your app has a login, include demo account info, and "turn on your back-end service". Apple says it will reject incomplete bundles and binaries that crash or show obvious technical problems.

The common-issues section adds that all links in your app must be functional, and that a link to user support with up-to-date contact information and a link to your privacy policy is required for all apps.

2.3 Accurate Metadata

Guideline 2.3 says your metadata, including privacy information, description, screenshots and previews, should accurately reflect the app's core experience. Keep it up to date with new versions. Under 2.3.3, screenshots should show the app in use, and "not merely the title art, login page, or splash screen".

4.2 Minimum Functionality

Guideline 4.2 says your app should include features, content and UI that elevate it beyond a repackaged website. If it is not particularly useful, unique or "app-like", it may not be accepted. Under 4.2.2, apps shouldn't primarily be marketing materials, web clippings, content aggregators or a collection of links, with catalogs as an exception. If you wrapped your website and called it an app, read this one twice.

5.1.1 Data Collection and Storage

Under 5.1.1, all apps must link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible way. The policy must say what data the app collects, how, and what it is used for. It must also cover third parties such as analytics tools and SDKs, and explain how long you keep data and how a user can request deletion.

If your app supports account creation, you must also offer account deletion within the app. This is in 5.1.1 (v). Apple's account deletion page says the option should be easy to find, typically in account settings. It says offering only to temporarily deactivate or disable an account is insufficient.

Sign-in and demo accounts

The App Review Information section in App Store Connect is where this goes. Apple's page on App Review information says the demo account is used during review and "must not expire". The Notes field is for anything needed to test the app, such as app-specific settings. It also asks for a contact person in case App Review needs more information.

A check to run before you submit

  1. Install the build on a real device, as a fresh install, and use it like a stranger would.
  2. Open every link in the app and in your App Store listing. Fix or remove the dead ones.
  3. Search the app for placeholder text, test images and empty screens.
  4. If there is a login, create a demo account that works and does not expire. Put it in App Review Information. Make sure your back end is running.
  5. Add anything special to the Notes field: settings, hardware, how to reach a hidden feature.
  6. Check that your privacy policy URL works, is in App Store Connect and is linked inside the app, and that it matches what your app and SDKs really collect.
  7. Compare your screenshots with the app. They should show the app in use, not just a login or splash screen.
  8. If users can create an account, find the delete account option and use it once.
  9. If you sell in-app purchases, buy, restore and cancel once in the sandbox. See testing in-app purchases.
  10. Make sure your support link and contact details are up to date.
  11. Ask yourself if this is more than a website in a frame, and if it does enough to be useful.

If you are rejected anyway

Read the message first. Apple's page on replying to App Review messages says you open the app in App Store Connect, click the link about unresolved issues, click Resolve next to the submission, and use Reply to App Review. The role needed is Account Holder, Admin or App Manager. You can write back and attach screenshots until you resubmit. Apple adds that if the rejection was for a metadata issue, you can resubmit the same build after fixing it.

Usually the quickest path is to fix what the message names and submit again. If you think Apple misunderstood your app or treated you unfairly, Apple says you may appeal to the App Review Board. Apple's advice is to give specific reasons why your app complies with the guidelines, submit only one appeal per submission that didn't pass, and answer any requests for more information before you appeal.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps. It is not affiliated with Apple, and it does not guarantee that your app will be approved. What it can do is put outside testers on your build before App Review sees it. Strangers on TestFlight can catch crashes and broken flows that you stopped noticing weeks ago. I covered TestFlight in TestFlight beta testing: external testers and public link.

  • Makers post web, iOS and Android apps with a link testers can open or install, like a TestFlight link.
  • You can add a test login that only signed-in testers see.
  • Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1.
  • The maker can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.

A TestSwap review is a written review on TestSwap, not a pass from Apple. Give testers one clear job, such as "sign up, create one item, delete your account". I wrote about that in how to write a test task. For more ways to find people, see how to find beta testers for your app.

Try it

If you want outside eyes on your build before you submit, post your app on TestSwap with a test task that says exactly what to do. You get 3 credits to start, and reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).