Invalid or Non-Increasing CFBundleShortVersionString

Question

macktek OP

Created Oct ’15

Replies 5

Boosts 0

Views 10k

Participants 6

When uploading a build today, I got the following message from iTunes Connect:

Dear developer,

We have discovered one or more issues with your recent delivery for "Synacor Watch". To process your delivery, the following issues must be corrected:

Invalid or Non-Increasing CFBundleShortVersionString - The value specified in the bundle's Info.plist file for the key CFBundleShortVersionString must be a string consisting of at most three dot-separated components, where each component is composed only of the digits 0 through 9. For example, any of the following are syntactically valid values for CFBundleShortVersionString: "1.0", "4.2.1", "3.46", "1.112.0"; whereas the following are all syntactically invalid: "1.4.0.0.0.0.5", "GX5", "3.4.2b6", "2.6GM", "1.0 (Gold)", "-3.6". Additionally, each updated version of the same application must have a CFBundleShortVersionString that increases relative to that of the previous version that was actually made available for sale on the iTunes Store. For example, if a previously-available version had a CFBundleShortVersionString of "1.4", then any of the following would be acceptable as the next update: "1.4.1", "1.4.332", "1.5"; but all of the following (though syntactically valid) would be unacceptable: "1.4", "1.3", "1.3.9", "0.9". For more information about the CFBundleShortVersionString key and the Info.plist file, see Apple's Runtime Configuration Guidelines at http://developer.apple.com/library/ios/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

The problem with this email is that it just isn't true. I uploaded a build yesterday (v1.0b35) but today when I tried to upload v1.0b36 it failed with this email. I used the same process I always use for every build (since v1.0b1) and it's worked flawlessly. Any ideas?

Boost

Answer 1

fouquet OP

Oct ’15

Same problem here. My CFBundleShortVersionString is "3.0". Should work just fine, yet I get this Email and the buid is not being processed.

0

Answer 2

thomasrzhao OP

Oct ’15

I had the same issue. I had a third party dynamic framework included, and for some reason Apple is checking that bundle's short version string as well. I would go through all your bundles and update the Info.plist to match your app's.

It doesn't really make sense for other bundles' version strings to have to match the app's so this seems like a bug on Apple's end.

0

Answer 3

rromanchuk2 OP

Oct ’15

Filed 23210422, can't upload anything.

0

Answer 4

RodSP OP

Oct ’15

Was just able to upload without the "CFBundleShortVersionString" error. Not sure if it was a change I made, or the fix was on Apple's side.

Had a version of 3.40 with a build of 127

This was failing from builds 122 - 127.

I just uploaded 3.40 (no change) with build 128 (next number). As it looked like at first, thinking this would fail again, I uploaded a new version, this time with a new version increase: 3.41 build 129.

Before, 3.41 was fully uploaded, my previous upload (3.40 128) was successfully uploaded (the build was clickable in iTunesConnect), and so I canceled the 3.41

Conclusions?

Either it was fully fixed on Apple's side, of changing the version number refreshed something. I believe the former.

Prior to that, I was suspecting the zero after the number 3.40 (resulting in float version number ‘3.4'). Guess I’ll find out in version 3.50

0

Answer 5

jo3rw OP

Nov ’16

Found the answer here: http://stackoverflow.com/questions/4933093/cfbundleversion-in-the-info-plist-upload-error

Basically it is a bug and you have to increment the 1st version number if you want it to go through. So if you were on 3.40 your going to have to use 4.0.

0