Repository navigation
|
My app was flagged or rejected on App Store for this. Debug or test features shipped in the production build. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. 2.1 (App Store) Severity in the playbook. high What triggers it. Debug menus, test logins, or developer backdoors left visible in the release build rather than gated behind a debug only flag. What to search your code for. How to fix it. Hide debug and test features behind a debug only compile flag so they never ship in production. Source. lukylab checklist. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. 2.1 (App Store)
Severity in the playbook. high
What triggers it. Debug menus, test logins, or developer backdoors left visible in the release build rather than gated behind a debug only flag.
What to search your code for.
debug menu,debugMenu,test login,skip login,bypass auth,DEBUG_BYPASSHow to fix it. Hide debug and test features behind a debug only compile flag so they never ship in production. Source. lukylab checklist.
The guard reports this as
APPLE-2.1-DEBUG-FEATURES. The full pattern is in data/rejection-patterns.json.This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts…