App Review Rejection Decoder

1. The guideline number is a category, not the reason. "2.1" covers everything from a crash to a missing demo account. Fix what the sentence under it says. We once fixed seven real defects after seeing only the numbers; Apple had asked about one of them.
2. If you cannot reproduce it, ask. Reply and ask for the exact steps and screen. A single sentence back from the reviewer (for example "the app stays on the login page until we relaunch it") can point straight to the cause.
3. Reply to each citation separately, and name the concrete change for each. "We fixed the issues" tends to come back as the same rejection.
4. Only claim what you tested. If something could only be checked on a simulator, say what you checked.
5. Test on the device Apple used. Reviews often run on an iPad even when the app was designed for iPhone.
6. Some items need only a reply (a price confirmation, a demo account, metadata). Others need a new build with a higher build number.

Want someone to handle it?

Rejection fix, $99: we read the full message, find the cause, make the fix in your project, upload a new build and draft the reply for your approval. Target turnaround 72 hours from access. Apple still makes the final decision, and its review time is separate.