App Store 2.3.1 rejection: Hidden features and misleading claims

Your app may behave differently for the reviewer than it does for customers. Guideline 2.3.1 requires Apple to see and understand the features being submitted. It also addresses misleading claims about what the app does or costs.

2.3.1(a): make the actual behavior reviewable

Check remote configuration, account roles, region restrictions, and features activated after approval. Describe substantive changes specifically in Notes for Review, and provide the access needed to use them. We’d compare your review account with an ordinary customer’s account to find accidental differences too.

Correct misleading claims in the app, store listing, and external marketing. A feature that says it scans iOS for viruses needs scrutiny of what it can actually do; a disclaimer doesn’t make an impossible capability real.

2.3.1(b): repeated or serious misconduct

Apple treats serious or repeated dishonest behavior as grounds for removal from its developer program. Address the underlying behavior across releases and campaigns, rather than hiding the single example in the notice.

Verify and explain

Test every relevant account role and feature switch. Give Apple the feature location, access steps, and accurate notes for the corrected build. If the difference was a configuration mistake, explain it plainly with evidence.