Use CFBundleShortVersionString instead of kCFBundleVersionKey when present

[coneybeare]

A common project setup is to increment the bundle version every build and use the short version string to display the human readable version.

For example,

CFBundleVersion => 1439
CFBundleShortVersionString => 1.0.2

I think that if the CFBundleShortVersionString key exists, it should be used for comparison and display in the app, not the CFBundleVersion

[nicklockwood]

Good call, I'll look at adding a check for it.

In the meantime, you can override the version number manually in your iVersion setup by saying

[iVersion sharedInstance]. applicationVersion = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"CFBundleShortVersionString"];

But you probably knew that already ;-)

Nick

On 18 Nov 2011, at 14:25, Matt Coneybeare wrote:

A common project setup is to increment the bundle version every build and use the short version string to display the human readable version.

For example,

CFBundleVersion => 1439
CFBundleShortVersionString => 1.0.2

I think that if the CFBundleShortVersionString key exists, it should be used for comparison and display in the app, not the CFBundleVersion

---

Reply to this email directly or view it on GitHub:
#7

[nicklockwood]

As of iVersion 1.7.1, CFBundleShortVersionString is now used preferentially if available