Repository navigation
|
How can a team catch Metadata promises features that do not ship in this 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. 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 or in app copy uses coming soon, beta, or a promised feature not present in the build. Mirrors the fastlane precheck future_functionality rule. The fix. Describe only what the build does today. Remove coming soon and future feature promises from the listing. 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-FUTURE-FUNCTIONALITYwith a coverage line and a proper exit code.What the hit means. Listing or in app copy uses coming soon, beta, or a promised feature not present in the build. Mirrors the fastlane precheck future_functionality rule.
The fix. Describe only what the build does today. Remove coming soon and future feature promises fr…