nicklockwood/iNotify — Issue #1: Default value for MaxVersion isn't high enough for datestamp build numbers
Author: duanefields
Created: 2012-01-25 16:44:37+00:00
State: open

Our build system uses a datestamp string for the app version number, which represents a build number. We then use the the bundle version for the 'marketing version'. So a typical build for us is something like "20110101011237". This is the "Bundle version". We use "Bundle String Short" as the marketing version like "1.0.2" or whatever.

The default value for MaxVersion is 9999999, which is too short, as it's always "less than" our build number.

The work around is easy enough, remember to set a MaxVersion on all your news items, but the "fix" is also easy - just changed the default fallback value for MaxVersion to "9999999999" which will preserve the intention of the feature.

However, I wonder if it should refer to the bundle version CFBundleShortVersionString first, since this is the public facing "version" of the app that you might think of in regards to MaxVersion.