Repository navigation
|
How can a team catch Broken support, marketing, or privacy URL in the listing automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. python3 scripts/metadata-audit.py ./metadata --check-urlsRead 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. A support URL, marketing URL, or privacy policy URL in the listing does not load. Mirrors the fastlane precheck unreachable_urls rule. The fix. Confirm every listing URL is public and loads during the entire review window. 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
BOTH-UNREACHABLE-METADATA-URLwith a coverage line and a proper exit code.What the hit means. A support URL, marketing URL, or privacy policy URL in the listing does not load. Mirrors the fastlane precheck unreachable_urls rule.
The fix. Confirm every listing URL is public and loads during the entire review window.
Recipe source. d…