Rejection Decoder

Paste your App Store rejection. See what it means and what to do next.

Then see what happened to other developers who got the same line.

Try an illustrative sample: · ·

Runs in your browser. Your text is not sent or stored anywhere.

Rejections we explain

2.1(a) App Completeness2.1 Information Needed2.1(b) In-app purchases not found2.3 Accurate Metadata2.3.10 Other platforms in metadata2.3.14 Creative assets2.5.2 Downloading or executing code2.5.19 Hidden or undocumented features3.1.1 In-App Purchase required3.1.2 Subscriptions4.0 Design4.2 Minimum Functionality4.3(a) Spam: similar binary, metadata, or concept4.3(b) Spam: saturated category4.8 Login Services5.1.1 Privacy: data collection and storage5.1.2 Data use, sharing, tracking, third-party AI1.2 User-generated content1.5 Developer information5.6.1 App Store Reviews: custom rating prompts

All guideline guides with one-line summaries

Recent public cases

20 cases logged from public posts. Outcomes as reported by the developer; most are still unknown.

ApprovedX · @brol1dev · Jul 11, 2026

4.3(a) on a new app, approved a month later after a demo video

Approved July 4 after a June 3 rejection, as stated by the developer (about one month).

ApprovedX · @robmukh · Apr 14, 2026

4.3 Design Spam, approved 12 hours after a one-color change

Approved about 12 hours later, as stated. The post says 4.3 Design Spam without a sub-letter.

ApprovedX · @RobinTanDev · Oct 19, 2026

4.3(a) on an update, approved after a later retry

Approved, per the post. Time to approval not stated.

Stopped tryingX · @krPorsche918 · Oct 6, 2026

Five apps rejected under 4.3 in the same minute

Developer stopped new iOS launches, per the post. Guideline cited as 4.3 without a sub-letter.

Outcome unknownX · @MattBusel · Oct 19, 2026

11 apps rejected for 4.3 in 30 seconds, appeals unanswered

No reply to appeals after 14 days, as of the post. Final outcome unknown.

Outcome unknownX · @DanielMiara · Aug 28, 2026

Normal update to an approved app rejected under 4.3(a)

Outcome unknown.

See all 20 cases

How the decoder works

Rejection Decoder reads the rejection message you paste from App Store Connect and matches it to the App Store Review Guideline it cites. It looks for the guideline number first, then for phrases App Review typically uses for each guideline, so messages without a number still get matched. It covers the 20 guidelines above plus 4.1(a), 5.6, 2.3.1.

For each match you get a plain-English meaning, the usual next move (reply only, fix the listing, or ship a new build), fix steps, a reply outline, and real public cases from developers who got the same rejection. The matching runs in your browser; your text is never sent anywhere. Read the full methodology.

Based on Apple's App Review Guidelines as revised October 16, 2026. Last checked .