Am I actually required to update the CFBundleVersion regularly? #2776
-
|
I've came across an issue recently where sparkle says my app is up-to-date (when its not) when the CFBundleVersion is the same as the previous. I don't exactly have a workflow so incrementing build numbers so its really an afterthought for some of my small projects. Primarily using the CFBundleShortVersionString for the versioning system, I use Xcode to build and distribute. Am I actually required to update the CFBundleVersion regularly? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Yes it's an expectation for macOS apps that the CFBundleVersion is updated, even outside of Sparkle. If you do not care much about it, just set the CFBundleShortVersionString and CFBundleVersion to the same x.y.z string. For Sparkle's purposes, CFBundleShortVersionString is a human displayable version while CFBundleVersion is the logical compared version. |
Beta Was this translation helpful? Give feedback.
-
|
That's not an entirely bad idea to keep both build and version the same, will do that. |
Beta Was this translation helpful? Give feedback.
Yes it's an expectation for macOS apps that the CFBundleVersion is updated, even outside of Sparkle. If you do not care much about it, just set the CFBundleShortVersionString and CFBundleVersion to the same x.y.z string. For Sparkle's purposes, CFBundleShortVersionString is a human displayable version while CFBundleVersion is the logical compared version.