App Store & Google Play rejection help
Rejected by the App Store? I fix rejections.
You've finally submitted, and back comes a message from App Review quoting guideline numbers. It's a horrible feeling, especially when the app works fine on your phone. The good news: most rejections are fixable, and the message usually tells you more than it first seems.
I'm Emma, a senior React Native developer. I read the rejection, work out what the reviewer actually wants, fix it, and help you get back into review.
Common reasons
Why apps get rejected.
The usual suspects, with the Apple guideline number you'll see in the message.
Guideline 2.1
App Completeness
The app crashed during review, showed placeholder content, or the reviewer couldn't get past the login screen. A missing demo account is one of the most common causes.
Guideline 2.3
Accurate Metadata
Screenshots, the description or keywords don't match what the app actually does.
Guideline 4.2
Minimum Functionality
The app feels like a website in a wrapper, or doesn't do enough yet. This comes up a lot with AI-built apps.
Guideline 5.1.1
Data Collection and Storage
A missing privacy policy, permission requests without a clear reason, or no way to delete an account from inside the app.
Guideline 3.1.1
In-App Purchase
Selling digital content or subscriptions without using Apple's in-app purchase.
Google Play
Policy and Data safety
A Data safety form that doesn't match what the app does, missing policy declarations, or a target API level that's too old.
How I fix it
How I fix a rejection.
Read the rejection properly.
The guideline numbers, screenshots and reviewer notes in App Store Connect or Play Console. The real issue isn't always the first thing the message mentions.
Work out what the reviewer wants.
Sometimes it's code, sometimes it's the store listing, and sometimes the reviewer just needs a clearer explanation or a demo account.
Fix the app or the listing.
I make the change, test it, and send a new build through TestFlight or internal testing before it goes back to review.
Reply, resubmit or appeal.
I help you write a clear reply to the reviewer. If the rejection looks wrong, I'll help you appeal it.
Why me
I've been through review many times.
- 11+ years of commercial experience, mostly React Native.
- Releases at scale: white-label apps with around ten iOS and Android releases going out at once.
- Teaching: my React Native course on freeCodeCamp (opens in a new tab) has 450k+ views.
- My own app: Pronuntia is live on the App Store and Google Play. See my work
FAQs
Rejection questions.
Will my app definitely be approved after you fix it?
I can't promise that, because approval is Apple's or Google's decision. What I can do is fix what the reviewer flagged, check for other problems likely to come up next time, and make sure your reply explains the changes clearly.
Do I need to give you my Apple account password?
No. You can invite me to your team in App Store Connect or Google Play Console with a limited role, and remove me when we're done. Please don't send passwords or signing certificates through the contact form.
What if I think the rejection is wrong?
It happens. Reviewers sometimes miss a feature or misread how the app works. I'll help you reply with a clear explanation, screenshots or a short demo video, and if that doesn't settle it, appeal the decision.
Get help
Got a rejection? Send it to me.
Paste the rejection message into the form and tell me what the app does. I'll explain what it means and what it'll take to fix.
Get help with a rejection