Release readiness joins product behavior, metadata, permissions and distribution configuration. A local review can organize checks, but only the real submission process establishes acceptance.

Working build → Privacy and metadata → Signed archive → Submission review
  1. 1Working build
  2. 2Privacy and metadata
  3. 3Signed archive
  4. 4Submission review

Work through the example

Create an evidence checklist with owners and unresolved items. Keep unsupported or untested capabilities out of release claims.

Start with a disposable branch and synthetic data. Write the expected outcome before changing the implementation, then keep the first failing result. This prevents a later repair from quietly redefining the task. The procedure below is grounded in the repository reference; its examples must still be checked against your project and installed toolchain.

Implementation reference

The following focused section is adapted from the maintained project guide. It preserves the source’s examples and limitations.

Privacy

  • [ ] Privacy policy URL provided (required for all apps)
  • [ ] Privacy policy is accessible and clearly written
  • [ ] App Privacy labels configured in App Store Connect (Data Types questionnaire)
  • [ ] Each data type categorized correctly (collected vs. tracked vs. linked)
  • [ ] App Tracking Transparency (ATT) prompt implemented if tracking users across apps
  • [ ] ATT prompt shown before any tracking begins
  • [ ] NSUserTrackingUsageDescription added to Info.plist if using ATT
  • [ ] Purpose strings (usage descriptions) provided for all permission requests:
  • [ ] NSCameraUsageDescription
  • [ ] NSPhotoLibraryUsageDescription
  • [ ] NSLocationWhenInUseUsageDescription
  • [ ] NSLocationAlwaysAndWhenInUseUsageDescription (if applicable)
  • [ ] NSMicrophoneUsageDescription
  • [ ] NSContactsUsageDescription
  • [ ] NSCalendarsUsageDescription
  • [ ] NSBluetoothAlwaysUsageDescription
  • [ ] NSFaceIDUsageDescription
  • [ ] NSHealthShareUsageDescription / NSHealthUpdateUsageDescription
  • [ ] Each purpose string clearly explains why the permission is needed (in user-friendly language)

Acceptance and failure review

Checkpoint What to inspect If it does not match
Working build Confirm the input and environment Preserve the failure and return to this step
Privacy and metadata Inspect the intermediate artifact Preserve the failure and return to this step
Signed archive Run the focused check Preserve the failure and return to this step
Submission review Record the observed result Preserve the failure and return to this step

Ask the agent to explain the smallest change that resolves the observed mismatch. Keep unrelated refactors out of the repair. A change that makes a warning disappear is not enough if the behavior or ownership contract has changed. Re-run the same acceptance check so the before and after results are comparable.

Evidence and limits

No app was submitted to App Review for this series.

This is an educational guide. Its presence in the series does not certify a completed client-specific lab. The series evidence record separates executed checks from exercises and blocked environments.

Inspect the source used in this lesson.

What to do next

Next: Privacy manifests, permissions strings and the things agents leave blank