Repository navigation
|
How can a team catch Debug or test features shipped in the production build automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rni 'debug menu\|debugMenu\|skip login\|bypass auth\|DEBUG_BYPASS' --include='*.swift' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Debug menus, test logins, or developer backdoors left visible in the release build rather than gated behind a debug only flag. The fix. Hide debug and test features behind a debug only compile flag so they never ship in production. Source. lukylab checklist. Recipe source. data/detection-recipes.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 |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
APPLE-2.1-DEBUG-FEATURESwith a coverage line and a proper exit code.What the hit means. Debug menus, test logins, or developer backdoors left visible in the release build rather than gated behind a debug only flag.
The fix. Hide debug and test features behind a debug only compile flag so they n…