Error uploading only Mac Catalyst build of App through App Store Connect

Question

venkatg OP

Created Sep ’22

Replies 4

Boosts 0

Views 2.1k

Participants 4

Every time I try to upload the Mac Catalyst build of my App to App Store Connect, I get the following error:

Asset validation failed
This bundle is invalid. The value for key CFBundleVersion [3] in the Info.plist file must contain a higher version than that of the previously uploaded version [8]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion (ID: 60d6b17f-ea3e-4e82-a6e6-21c18e6fb9ef)

I have tried updating the version and build numbers in Xcode - still getting the same error. The Info.plist also looks fine - it just contains $(CURRENT_PROJECT_VERSION) next to Bundle version.

The kicker is that I'm having no issues with uploading iOS builds - only Mac Catalyst builds. Any help would be appreciated - I've been stuck on this problem for months!

I'm running Xcode 14 on macOS 12.5.1

Answered by Frameworks Engineer in 728165022

You must define CURRENT_PROJECT_VERSION in your target’s Build Settings as a user-defined build setting for it to expand to the desired value in your Info.plist.

Boost

Answer 1

Frameworks Engineer OP

Apple

Sep ’22

Accepted Answer

You must define CURRENT_PROJECT_VERSION in your target’s Build Settings as a user-defined build setting for it to expand to the desired value in your Info.plist.

1

Answer 2

venkatg OP

Sep ’22

Thank you, that solved the issue! I think it's still sort of buggy behavior that setting the build number in General settings of target doesn't work for this.

0

Answer 3

NateP OP

Dec ’22

For anyone else struggling with this error, the problem is that Mac requires the build number to be higher across versions. Here is the relevant text:

Important: For macOS apps, build numbers must monotonically increase even across different versions. In other words, for macOS apps you cannot use the same build numbers again in different release trains. iOS apps have no such restriction and you can re-use the same build numbers again in different release trains.

From this tech note:

https://developer.apple.com/library/archive/technotes/tn2420/_index.html#//apple_ref/doc/uid/DTS40016603-CH1-HOW_THESE_NUMBERS_WORK_TOGETHER

Confusingly, it did let me reuse a build number one time, but then balked after that.

0

Answer 4

cht1995 OP

Aug ’24

This is bothering. We had the same issue for our recent (initial) macOS release and dang, now we are stuck with a huge CFBundleVersion number for macOS: https://developer.apple.com/forums/thread/759988 😩

0