Repository navigation
|
How can a team catch Backend points at staging or localhost 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 -rn 'localhost\|127.0.0.1\|staging\.\|ngrok\|http://' --include='*.swift' --include='*.plist' . | grep -v httpsRead 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. API base URL in the release config contains localhost, 127.0.0.1, staging, dev, or ngrok. The fix. Point the release build at the live production backend and confirm it stays up during review. 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-STAGING-BACKENDwith a coverage line and a proper exit code.What the hit means. API base URL in the release config contains localhost, 127.0.0.1, staging, dev, or ngrok.
The fix. Point the release build at the live production backend and confirm it stays up during…