XCode 4.6: iOS 6.1 - CFBundleVersion and CFBundleShortVersionString errors when checking

enter image description here

I've changed the "Bundle version" and "Bundle version string, short" values ​​seemingly a hundred times with all the different flavors 1.2, 1.201, 2, 1.2.1 ... etc. Also, I changed the version numbers in the target> Summary tab.

Has anyone had this problem while checking the archive or when downloading through the old app loader? I also got the same search error for "CFBundleVersion". The last update for the app was v1.13, so I'm not sure why the problem is 1.2. Is this an XCode 4.6 bug?

+3


source to share


1 answer


Problem solved thanks to user comments and some, well, problem solving ...

When I downloaded XCode 4.6 I am using SmartSVN / VisualSVN for version control. When I updated SmartSVN to the latest version, I got a dialog that says Xcode doesn't support the SVN version (which is the latest version), so I decided to commit after I changed the package versions in the .plist. Blammo ... package checked and sent!

Here's what I found out that I actually did the trick. Xcode 4.6 should have new version requirements as the package version was still set to 1.0 when I tried it the first time. I submitted versions 1.0, 1.1, 1.12 and 1.13 ... so Xcode only had to check the versions in the TARGETS> Summary tab. They were always tuned to the correct version.



The kicker is something I didn't know Xcode sees 1.2 <1.13. As soon as I changed the values ​​in the .plist AND the values ​​in the TARGETS> Summary tab to "1.20", the package was validated successfully as 1.20> 1.2 and 1.20> 1.13 ... thanks for shining bright guys.

NOTE. If you are using a version controller, make sure you commit it before building if you get an Xcode warning that you don't support the SVN version.

+2


source







All Articles