What this rejection means
Guideline 2.3 covers everything people see about the app before they download it. A 2.3 rejection can arrive on a first submission or on an update where only the listing changed, and in any language the listing is published in.
What is at stake
A metadata rejection blocks the whole release, even when the build itself is ready. It also tends to repeat when the listing is published in several languages.
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
The rules on metadata are spread across several sub-points and Apple's own guidance, and what is accepted depends on context. The listing also has to keep selling the app once it complies.
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
Does this affect our store optimization?
Yes. The same listing drives search and conversion, so it has to work for both. See our ASO consulting.
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.