Catch App Store rejections
before App Review does.
Storewatch checks the version you are about to submit: What’s New in every language, text limits, the demo account, review notes and the build. Then an AI reads your listing against Apple’s App Review Guidelines and lists the risks with guideline numbers and fixes. It can’t promise approval, and it tells you what it doesn’t check.

What a rejection checker can and can’t see.
App Review rejects a submission for reasons in three groups. Some sit in your App Store Connect record: an empty field, a missing demo account, a build that doesn’t match the version. Some sit in your listing text: claims that don’t match the app, keywords that break the rules. And some sit in the app itself: a crash, a placeholder screen, a login that fails on the reviewer’s device.
Storewatch is a Mac app that reads your App Store Connect data. It can check the first group and read the second. It can’t run your app, so the third group stays your job. The table below says which row is which, so you don’t trust a green tick for something it never looked at.
The other pages cover the neighbours of this one: the guidelines in plain English, how long review takes and a first submission for apps built with AI.
Check first.
Red rows block.
Red rows block Submit for Review. Amber rows are advice. Running the check changes nothing in App Store Connect.

Which rejection causes Storewatch checks.
Every row marked “Checked” comes from a rule in the app. Everything else is marked “Not checked”, and for those the work is in App Store Connect or in your build. Guideline numbers are from Apple’s App Review Guidelines.
| Cause | Guideline | In Storewatch | What it does, or what to do |
|---|---|---|---|
| What’s New empty in some or all languages | 2.3.12 | Checked, blocks | Red row naming the languages. Only tests that text exists. Whether it describes the changes is for the AI check or for you. |
| A field over its character limit | 2.3.7 (name, 30) | Checked, blocks | Title and subtitle 30, keywords 100, promotional text 170, description and What’s New 4,000, in every language. |
| Sign-in required but no demo account | 2.1 | Checked, blocks | Red only when the version says sign-in is required. It checks that a demo user name is filled in. The password is never read. Apple says the demo account must not expire; that isn’t checked. |
| Notes for App Review | 2.3.1(a) | Checked, advice | Amber when empty. It can’t tell whether notes are specific, and Apple says generic descriptions are rejected. |
| Repeated, duplicate or wasted keywords; untranslated languages | 2.3.7 | Checked, advice | “Listing review found N problems”, marked not required for submitting. |
| Build for this version number | Upload step | Checked, blocks | Red for “No 4.4 build uploaded” or an expired or invalid build. Amber while Apple is still processing. |
| Names, prices or trademarks in metadata; text that doesn’t match the app | 2.3.7, 2.3 | AI check | Read by the AI against the guidelines. A judgment, not a rule. |
| Crashes, bugs, placeholder content, dead links | 2.1(a) | Not checked | Test the exact build on a device. Open every URL in the listing. |
| Screenshots that don’t show the app in use | 2.3.3 | Not checked | Look at them next to the build. The AI check reads text, not images. |
| Privacy policy link in the metadata and in the app | 5.1.1(i) | Not checked | Add it in App Store Connect and inside the app. |
| Terms of Use and privacy links for subscriptions | 3.1.2(c) | Not checked | Apple’s subscription page says the app and the metadata must include both links. |
| Contact details in App Review Information | Before You Submit | Not checked | Name, email and phone, with the phone number in international format. |
| A thin or repackaged-website app | 4.2 | Not checked | It depends on the app, not the listing. Explain native features in the review notes. |
Not checked doesn’t mean low risk. It means Storewatch can’t see it, so it won’t pretend to.
What the AI guideline check does.
The button “Check Against App Review Guidelines with AI” sits under the pre-submission rows. It opens Ask Storewatch with a ready question: check the listing for the version being prepared against Apple’s App Review Guidelines and list likely rejection risks with guideline numbers and fixes. It uses the AI you already set up, so it needs one.
In a real run on the sample app, it flagged a French listing that was mostly English under 2.3. It passed the field lengths, passed What’s New under 2.3.12 and passed names and prices under 2.3.7. That is the useful shape of the answer: what is wrong, which guideline, what to change, and what it found fine.
It is a second reader, not App Review. Models can miss a risk or flag one that isn’t real, so treat each line as something to look at, then fix or dismiss it. Nothing is changed in your listing unless you act on a fix.
What Apple publishes about rejections.
Apple’s 2025 App Store Transparency Report says App Review handled 9,100,620 app submissions that year and rejected 2,093,244 of them, nearly one in four. Apple notes that one app can be submitted several times, so these are submissions, not apps. It also says 387,087 submissions were approved after a rejection. Apple’s announcement of the report splits the rejections into over 1.2 million new apps and nearly 800,000 app updates. A year earlier, in 2024, it reviewed 7,771,599 submissions and rejected 1,931,400.
The report counts rejections by guideline section, and a submission can count under more than one. Performance (section 2) was the largest in 2025, with 1,354,418. Then came Legal with 495,673, Design with 415,532, Business with 283,820 and Safety with 151,159. Section 2 holds App Completeness (2.1) and Accurate Metadata (2.3), which is where most of the checks above point.
The report doesn’t rank individual guidelines for rejections, so any “top 5 rejection reasons” list is someone’s experience, not an Apple number. How fast review is, and how to read your status, is in the review times post.
Rejected anyway?
Keep a record.
A rejected submission gets a log entry: version, guideline, status and what you changed. AI can draft your reply.
A routine for the day you submit.
- Test the exact build. Install the build you uploaded, on a device, with the backend live. Apple’s “Before You Submit” list starts here. Storewatch can’t do this step.
- Open Releases and read the red rows. Fix What’s New, limits and the demo account first. They block the button.
- Write the review notes for a stranger. Apple’s help says the Notes field holds up to 4000 bytes, so accented or non-Latin text uses it up faster. Name where to find each new feature and any in-app purchase.
- Run the AI guideline check and go through each risk. Fix the ones that are real.
- Do the not-checked items by hand: privacy policy link, subscription links, contact details, screenshots and every URL.
- Attach the build and submit. After that, watch the status in Storewatch’s pipeline.
If a rejection arrives, reply in App Store Connect first. The Resolution Center guide has the steps and limits, and the guidelines post covers appeals to the App Review Board.
Questions, answered.
Does Storewatch guarantee my app passes App Review?
No. Nothing can. Apple’s reviewers decide, and some causes can’t be seen from the listing or the build record. Storewatch checks what App Store Connect lets it read and adds an AI read of your text against the guidelines.
Do I need an AI provider for this?
Only for the guideline check. The pre-submission rows run on your synced data and need no AI. The button “Check Against App Review Guidelines with AI” appears when you have an AI provider set up, such as Claude, ChatGPT, Claude Code or Ollama.
Does the check look at my screenshots or my build?
No. It reads the version’s text and the facts App Store Connect gives Storewatch: What’s New, field lengths, listing problems, demo account, review notes and build state. It doesn’t open the app, look at images or test for crashes.
Does Storewatch submit anything while I check?
No. Running the checks changes nothing in App Store Connect. Submit for Review is a separate button, and it stays off while a blocking row is red.
What if a submission comes back rejected?
Storewatch adds an entry to the Rejection log, with a note to paste Apple’s message into it. Apple’s Resolution Center text isn’t available to Storewatch, so you paste it, add what you changed, and can draft a reply with AI.
Sources: Apple’s App Review Guidelines, the 2025 App Store Transparency Report and Apple’s announcement of it (May 2026), the 2024 report, platform version information (App Review Information) and auto-renewable subscriptions. Checked November 2026.
Related: For AI app builders · Listing manager · Keyword field checker · AI agent · App Review Guidelines in plain English · Expedited review
Made by Alex, the developer of Storewatch. Last updated November 21, 2026.