iOS Build Environment Help Center

Setting Explicit Build Number Also Sets Version Number

append delete Dahaka

Hi,

I noticed in the App Store Connect upload tool that we can enable "Set the package build number while re-signing". It gives the option to use Auto increment, or explicit. When I set explicit, it seems to set BOTH the version and build number to that number. Would be nice to have it as different field (just as it is in Xcode), as this breaks our versioning for beta testing.

Thanks!

Reply RSS

Replies

append delete #1. Pierre-Marie Baty

Thank you for pointing me at this. It was this way because at the time this code was written (long, long ago, somewhere just after the great dinosaur extinction if I recall well) I couldn't make any meaningful difference between the CFBundleVersion and CFBundleShortVersionString keys in the Info.plist, and Apple wasn't clear about their meaning themselves. Now everybody seems to agree that CFBundleVersion is actually a build number and CFBundleShortVersionString is the displayed app version string. The only prerequisites are that they be both in the form X.Y[.Z], equal or consecutive to their previous value, and that the pair {version number, build number} thus formed be unique.

Consequently, it makes sense to just change the CFBundleVersion key when using the automatic numbering scheme, totally. This change will be in the next version.

append delete #2. Dahaka

Awesome, thanks for the quick response! Will be waiting for the new version. Will be be able to explictly target both version _and_ build number? I generally keep the same version and only increment my build, this way I don't have to wait for review on test flight (have to wait 24h if a different version, but not if an increment of build).

Really neat plugin btw, took me 5 min to setup (my prior experience with certificates helped a lot), and it might be psychological but feels like it's faster than Xcode.

append delete #3. Pierre-Marie Baty

The change I’ll make will be that when the automatic build numbering scheme option is used, only the build number (CFBundleVersion) will be set. The developer will remain in charge of setting and updating the version string (CFBundleShortVersionString) himself. It corresponds to what you’re saying.

Thanks for the appreciation. In theory the builder couldn’t be much faster than Xcode for a great number of reasons (I know many performance bottlenecks that could be optimized) - but in practice often it is. I’m not sure where Xcode spends its time comparatively, probably their linter/IntelliSense/whatever eats a lot of CPU even when a build is in progress. I won’t complain :-)

Reply

(Leave this as-is, it’s a trap!)

There is no need to “register”, just enter the same name + password of your choice every time.

Pro tip: Use markup to add links, quotes and more.

Moderators: Pierre-Marie Baty