Release quality · 2026-09-23

What to inspect after an App Store hidden-function rejection

Reviewers see the final signed artifact and reachable paths—not the developer’s source-code intent.

Separate five states first

Source removal, disabled compile conditions, removed signing capabilities, a clean exported IPA, and a newly selected review build are five different facts. Proving one does not prove the rejection cause is gone.

Inspect every reachable entry

Beyond buttons, inspect deep links, remote flags, notifications, background modes, URL schemes, hidden gestures, and stale state. Review notes should explain how the feature is entered, exited, and what a test account requires.

Finish with artifact evidence

Re-export and inspect entitlements, Info.plist, embedded frameworks, and permission strings, then confirm App Store Connect selects that build. Reply with verified facts only.