Digestplatforms
App store review and your marketing claims
By UA Ledger staff — Archive date: 2 min read
A rejected update after a creative refresh is usually a listing mismatch, not a creative problem. The fix is a claim-by-claim check before launch.
A rejected update after a marketing refresh is rarely a creative problem; it's a store listing mismatch, and it's one of the more avoidable rejections in review, because both stores publish the rules and apply them consistently even when a launch calendar makes them easy to skip.
Both major stores require screenshots to represent actual, shipping app functionality. A screenshot of a feature that isn't live yet gets rejected. So does gameplay captured from a build variant that differs from what a player actually downloads, which happens most often when a creative team pulls assets from an earlier concept build instead of the current release candidate.
Pricing claims draw similar scrutiny. An app with in-app purchases can't market itself as simply free without qualifying language once purchases materially gate content or progression; Apple and Google both flag listings where a headline price claim omits that a meaningful part of the experience sits behind a purchase.
Pre-order listings carry their own disclosure obligations. Expected release windows need to be accurate rather than aspirational. A listing cannot advertise features that aren't confirmed for the version a player is actually pre-ordering. And in-app purchase price ranges belong in the listing itself, not at the checkout screen a player only reaches later.
The subtler risk sits between the ad and the listing rather than inside either one alone. When a paid ad promises a mechanic or a reward that neither the store listing nor the first minute of play delivers, app review can flag the discrepancy and an ad platform's own quality signals can flag it separately. Repeated mismatches raise the odds of manual review on every future submission, and that queue is a slower, more expensive problem than fixing one listing.
Before a creative refresh goes live, run its central claim past the store listing and the first ninety seconds of the build, side by side. Matching them now costs less than defending a rejection later, and it keeps a studio out of the manual review queue, which is where a pattern of policy strikes eventually lands.
Related archive reading
These articles provide related context and remain subject to their stated review status.