Nanfeng

Notes on software development, code, and curious ideas

Fixing an Incorrect Build Number in an iOS Archive

In
How to fix an iOS archive whose version and build number do not match the values configured in Xcode.

While building the iOS version recently, I discovered a serious problem: the version uploaded to App Store Connect did not match the version I had built locally.

Archives showing the same version

At first, I did not pay much attention because all of my archives appeared to use the same version. When I was ready to submit the app for review, however, I could not find the build I had uploaded the previous day. Locally, it looked like this:

The expected local build

The 1.0.0 (8) build was missing from App Store Connect. After checking the project carefully, I found that setting Build = 8 in Xcode had not updated the Info.plist used by the final .app bundle.

Solution

  1. Find the Info.plist actually used by the archive. Open Build Settings and search for Info.plist File.
  2. Open that file in an editor. I prefer viewing it as XML.
  3. Find CFBundleShortVersionString and CFBundleVersion, then update their values.

For example:

1
2
<key>CFBundleVersion</key>
<string>8</string>

Manually editing the file before every archive is inconvenient. A better permanent solution is:

1
2
<key>CFBundleVersion</key>
<string>$(CURRENT_PROJECT_VERSION)</string>

The archived app will then use the current project build number automatically.

+