4 ms·
I see two problems here. First, the Marketing Version (which is CFBundleShortVersionString) is set to a rather ugly SHA1. Which will now show up in your applica
by terinjokes 16y ago
I see two problems here. First, the Marketing Version (which is CFBundleShortVersionString) is set to a rather ugly SHA1. Which will now show up in your application's about window, in Finder, and other places. Nice, but not quite.
You can't easily sidestep this by setting the SHA1 to CFBundleVersion, which is the internal build number. That's because you then break OSX's Launch Services. Why? Because LS expects a version number in the form of nnnnn[.nn[.nn]][X]
While not automate (but probably fairly simple to do so) I use the system described by Dave Dribin at http://www.dribin.org/dave/blog/archives/2006/08/02/versioning_os_x_apps/ http://www.dribin.org/dave/blog/archives/2006/08/02/versioni...
- SeoxyS 16y agoTrue, that is the one biggest downside. However, I fount it to be the best automated way to deal with this, short having a centralized database of build numbers. In the about window, it's an easy fix. The only place that you can't help having the git short hash is in the Finder, for a Mac app. For iOS apps, this isn't a problem.