Repository navigation
|
How can a team catch Metadata names an iOS bug or references Apple negatively 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 ./metadataRead 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. Listing copy mentions an iOS bug or makes a negative or insensitive reference to Apple. Mirrors the fastlane precheck negative_apple_sentiment rule. The fix. Remove negative references to Apple and iOS bugs from the listing copy. 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.3-NEGATIVE-APPLE-SENTIMENTwith a coverage line and a proper exit code.What the hit means. Listing copy mentions an iOS bug or makes a negative or insensitive reference to Apple. Mirrors the fastlane precheck negative_apple_sentiment rule.
The fix. Remove negative references to Apple and iOS bugs from the listing copy.
Recipe source. da…