What this rejection means
Guideline 2.1 asks that what you submit is complete and ready for people to use. The message names the guideline but often says little about what exactly the reviewer ran into.
What is at stake
Every round of review takes time, and a resubmission that misses the real cause usually comes back with the same answer. Repeated rejections push back launch dates and everything planned around them.
When to talk to us
- The message doesn't make clear what to change
- You resubmitted and got the same answer
- A launch, an update or a campaign is waiting on this
- You're not sure whether to reply, resubmit or appeal
Why it takes more than a quick fix
What the reviewer saw is not always what your team sees. Finding the real cause, and being sure it is gone before you resubmit, is where most of the time goes.
How we help
- You send us the caseThe reviewer's message, the app and what changed since the last approved version.
- We find the real causeWe look at your case the way the store does, and find what is really behind it.
- You get a clear planWhat has to change, written for your team, or we work on it with them.
- We help you answerYour reply to the reviewer or your appeal, and follow-up until the review is closed.
Questions
Our app works fine for us. Why was it rejected?
There are many reasons an app passes your own tests and fails review. Finding which one applies to yours is the first thing we do.
Can you guarantee approval?
No one outside Apple and Google can promise how a review will go. What we can do is find the real cause, remove what we can see would block approval and give the reviewer everything they need.
Do you need access to our accounts?
It helps, but it is your choice. We can work from screenshots, exports and a build, or with a limited role you add and remove yourself.