Missing version or build number on App Store Connect upload

App Store Connect needs two separate numbers: the marketing version people see on your product page, and the build number that distinguishes uploads of that version. They live in different build settings and it is common to set one and forget the other.

Can block submissionconfig.version

Why it matters

The marketing version is MARKETING_VERSION, shown as CFBundleShortVersionString in Info.plist. It is the version the App Store lists, and it has to increase for each public release.

The build number is CURRENT_PROJECT_VERSION, shown as CFBundleVersion. It distinguishes one upload from another within the same marketing version, and App Store Connect refuses an upload whose build number it has already seen. Every upload needs a new one, including the ones that replace a build you rejected yourself.

Because they resolve from build settings that Info.plist then references, a project can look correct in one place and be empty in the other. What matters is the value that resolves for the configuration you archive.

How to fix it

  1. Set MARKETING_VERSION in the target’s build settings to the version you want listed, for example 1.0.0.
  2. Set CURRENT_PROJECT_VERSION to a build number, and increment it on every upload rather than only on every release.
  3. If Info.plist carries literal values instead of $(MARKETING_VERSION) and $(CURRENT_PROJECT_VERSION), decide which of the two places is authoritative and remove the duplication, so there is one number to change.

The guidelines behind it

Read from Apple’s App Review Guidelines as last updated October 16, 2026.

What ReviewAhead checks

Version and build number. App Store Connect requires a marketing version and a build number.

  • That a marketing version resolves for the target, from build settings or from Info.plist.
  • That a build number resolves the same way.
  • Reports the value it found for each, so you can see which configuration it came from.

Apple’s own documentation for this requirement: developer.apple.com. Where this page and Apple disagree, Apple is right and this page is a bug.

Scan my projectScan your Xcode project and see whether this one is a problem in your app, free.

All 38 App Store readiness checks