- Home
- Rejection types
Every rejection, explained in plain English
A rejection message names a guideline number or a policy. Find yours below to read what it actually means, why apps built with AI tools get it, and what we do about it. If you're not sure which one you have, send us the message and we'll tell you.
How to read your rejection message
Apple sends an email saying the status of your app has changed, and the full message sits in your developer account next to the app version. It always starts with a number and a title, like "Guideline 4.2 - Design - Minimum Functionality". The number is the rule. The text after it is the reviewer explaining what they saw, often with a screenshot. One message can list several guidelines; each one needs to be dealt with.
Google Play sends an email too, and shows the same notice in Google Play Console under the app's policy status. Instead of a number it names a policy, like "Data safety" or "Deceptive behavior", and sometimes the exact screen where the reviewer found the problem.
Either way, the message is about what the reviewer saw on the day. It is not a judgment about you, and one rejection does not count against your account.
App Store rejections
iPhone and iPad appsGoogle Play rejections
Android appsSend us the message. We'll tell you what it means.
Paste the rejection exactly as you received it, with a link to your app if you have one. Within 24 hours you get a plain-English answer: what the reviewer is asking for, whether we can fix it, and what it would cost. No charge, no commitment.
Rejected under something not listed here?
The six guidelines above cover most rejections we see on apps built with AI tools, but Apple's guidelines run to dozens of sections and Google's policy center is longer still. Other ones we handle regularly include design and layout problems on iPad (Guideline 4.0), sign-in rules when an app offers social login (Guideline 4.8), kids' and medical content rules, and Google Play's permissions and families policies. If your message names something else, the fixed price still covers it. Send it to the free check and we'll confirm.
Two things are true for every rejection on this page:
- One order covers everything in the message, however many guidelines it lists, and however many rounds it takes.
- We make the changes inside your own project and your own developer account. The app is resubmitted from your account, under your name. We never ask for your password.
Rejections by builder
Each AI tool has its own habits, and so do the rejections that follow. These pages cover what we usually find for apps made with each one, and how to share your project with us.
Questions about rejections
Can one rejection list several guidelines?
Yes, and for AI-built apps it usually does. 4.2 with 2.1, or 5.1.1 with 2.3, are common pairs. One order covers all of them.
Is a rejection a strike against my account?
No. Rejections are a normal part of review and don't count against you. Repeated manipulative behavior, such as resubmitting the same app under new names, is what gets accounts in trouble.
How long do I have to respond?
There is no deadline. The submission stays rejected until you send a new one. If a reviewer asked for information, the request simply waits.
Do you only fix apps built with AI tools?
No. The service is built around apps made with Lovable, Bolt, Base44, Replit, FlutterFlow, v0 and Cursor, but the guidelines are the same for every app. If you can share the project, we can work on it.
What does the fix cost?
One fixed price, $249, for any rejection, with unlimited resubmissions and a full refund if the app is never approved. See pricing.
Rejected. Approved.
Share your project in two minutes. We review it within a day and get to work inside your own account.