> On 19 Aug 2020, at 9:07 am, Gabriel Zachmann via Cocoa-dev > <cocoa-dev@lists.apple.com> wrote: > > The plist file has, additionally to all the default stuff, the key > CFBuildNumber (with a value that I increment automatically). > > In Xcode, I tried to change "Bundle version" to a value like > > $(CURRENT_PROJECT_VERSION)_$(CFBuildNumber)
As an aside, it strikes me as a dubious idea to call the latter "CFBuildNumber". That sounds like the name of a well-known CoreFoundation key, but as far as I can tell, it isn't one. (A Google search for "cfbuildnumber site:apple.com" yields only two results for me, one of which is a Tech Note that seems to contain errors [1]). To avoid false inferences or potential confusion, if it were me I would use a completely different name for the key, such as "MyProjectBuildNumber" or whatever. (But why not just take advantage of the existing CFBundleShortVersionString and CFBundleVersion?) -ben [1] https://developer.apple.com/library/archive/technotes/tn2259/_index.html: Under the heading "What's Next", about a third of the way down, the text seems to confuse "CFBundleVersion" with what's actually CFBundleShortVersionString, and "CFBuildNumber" with what's actually CFBundleVersion. I've just filed a bug report on this: FB8464082. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com