Version Management
One version = version number + build number + metadata + screenshots + review notes. Self-check before submitting.
Version vs Build
- Version: User-facing (e.g., 1.2.3); must increment per your policy.
- Build: Internal number from CI/Xcode; must be higher than previous; tied to the version.
- Upload builds via Xcode/Transporter or CI (fastlane pilot/altool deprecated).
Pre-Submission Checklist
- Metadata complete: description, keywords, privacy policy, support and marketing URLs.
- Screenshots/videos: correct resolutions and devices; match actual functionality.
- App Privacy: correct data collection/use; verify third-party SDK purposes and tracking.
- Login apps: provide test account/password; add review notes for special environments.
- Permissions: camera/mic/location, etc., must have specific purpose strings.
Review and Release
- Choose Manual or Automatic release after approval.
- Optional phased release (percent rollout) or scheduled release.
- Common rejections: broken features, crashes, mismatched metadata, insufficient privacy disclosure, IAP unavailable.
Updates
- Each new version needs fresh “What’s New” text and a new build.
- For small fixes, you can resubmit same version with higher build; clearly describe changes.
- After approval, release immediately, schedule, or phase rollout.