Repository navigation
|
How can a team catch iCloud or CloudKit schema not deployed to production 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 'CKContainer\|CloudKit\|NSUbiquitousKeyValueStore' --include='*.swift' . # then confirm the CloudKit schema is deployed to production in the CloudKit consoleRead 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 uses CloudKit or iCloud but the schema and containers are only in the development environment, so the feature fails for the reviewer on the production build. The fix. Deploy the CloudKit schema and containers to production before submitting. Source. lukylab checklist. 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-CLOUD-NOT-IN-PRODUCTIONwith a coverage line and a proper exit code.What the hit means. The app uses CloudKit or iCloud but the schema and containers are only in the development environment, so the feature fails …