new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

App Store & Google Play Review · all subjects

Rejections and appeals

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

How do I appeal an App Store rejection, and does it work?

Two distinct moves, in Resolution Center inside App Store Connect. First, reply to the reviewer directly in the rejection thread: many rejections are misunderstandings fixed by a one-message clarification with a screenshot or video showing the flagged feature working. Second, if the reviewer maintains the rejection, appeal to the App Review Board from the same thread. The Board overturns rejections when you show the guideline was misapplied — quote the exact guideline text and map your app's behavior to it, cite approved comparable apps doing the same thing, and stay factual. Appeals that complain about business impact, deadlines, or reviewer competence go nowhere. Realistic Board response time is days to a couple of weeks; a well-argued Board appeal on a genuinely misapplied guideline succeeds often enough to always be worth filing before giving up.

Should I resubmit or appeal — what is the difference in outcome?

Resubmit when the rejection is factually right and fixable: crash, missing demo account, dead link, wrong screenshot. A fixed resubmission is faster than arguing. Appeal (or clarify in-thread) when the rejection rests on a wrong premise: the reviewer missed the feature (point to it, with a timestamped video), or applied the wrong guideline (explain why another guideline governs). Do not resubmit an unchanged binary hoping for a different reviewer — that pattern gets flagged and poisons future review times. If you both fix and dispute, say explicitly in review notes what changed. One nuance: metadata-only rejections can be resolved without a new binary by editing the listing and replying — do not push a new build for a screenshot problem.

When does Apple grant expedited review?

Expedited review is requested from App Store Connect (Contact Us → request expedited review) and is granted for two credible cases: a critical bug fix for an app already on the store (crash on launch, data loss, security issue), and time-sensitive events tied to a fixed external date (app linked to a conference, product launch, seasonal event). It is not for faster routine releases — abusing it burns goodwill and Apple tracks request frequency. In the request, state the specific bug or date, the affected version, and why the normal timeline fails you. Granted requests typically review within 24–48 hours. There is no equivalent formal channel on Google Play, but Play's review is usually faster; for urgent Play fixes, releasing to a high-percentage staged rollout still requires review.

What tone and evidence overturn rejections?

What works: short, factual, guideline-anchored. Structure: (1) quote the rejection and guideline, (2) state precisely what the app does, (3) explain the mismatch with evidence — a screen recording showing the feature, a document proving licensure, a link to the rule text, or names of live comparable apps, (4) one sentence asking for the specific outcome. What fails: long narratives, frustration, claims about revenue or investors, threats to leave the platform, and 'other apps do it' without naming them. If the rejection involves a factual claim about your business (licenses, permissions from IP holders, government authorization), attach the document — documentary evidence is the single strongest overturn lever. Keep everything in the Resolution Center thread so the record is complete for the Board.

How do I appeal a Google Play policy decision?

Play appeals go through the Play Console policy status page (the 'Appeal' button on the violation) — not email. You get one substantive shot per decision, so make it complete: address the exact policy named in the enforcement email, explain the app's actual behavior, attach screenshots/video or documentation, and if you already shipped a fix, give the version code where it is fixed. Play's reviewers respond in roughly a few days to two weeks; the response is often templated, so clarity matters. If an appeal is denied and the app stays removed, the only paths are a corrected resubmission (often under the same package name if the app was suspended but the account is healthy) or, for termination-level decisions, the formal appeal form linked in the termination notice.

Give your agent this brain