Repository navigation
|
How can a team catch CI pipeline calls a removed App Store Connect API age-rating endpoint 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 'appStoreVersions/[^ ]*/ageRatingDeclaration\|relationships/ageRatingDeclaration' --include='*.rb' --include='*.sh' --include='*.py' --include='*.js' --include='*.ts' --include='*.yml' --include='*.yaml' .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. The App Store Connect API removed GET /v1/appStoreVersions/{id}/relationships/ageRatingDeclaration and GET /v1/appStoreVersions/{id}/ageRatingDeclaration. A fastlane, script, or CI step that still calls them fails and the release pipeline stops. The replacement is the read age-rating declaration endpoint, which also carries the new socialMedia and socialMediaAgeRestricted attributes. The fix. Switch to the current age-rating declaration read and update endpoints, and set socialMedia and socialMediaAgeRestricted where the app has social features. Re-run the pipeline against a TestFlight build before the next release. 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-ASCAPI-AGERATING-ENDPOINT-REMOVEDwith a coverage line and a proper exit code.What the hit means. The App Store Connect API removed GET /v1/appStoreVersions/{id}/relation…