Crap, sent too fast: Android's version code needs to be an Integer: http://developer.android.com/tools/publishing/versioning.html
So, the inconsistency is a platform inconsistency it seems. I do think the marketing versions should match, but versionCode can't match. Also, versionCode is what has to be incremented every time there's a release so that an update happens on the Play Store. I think the complaint is that the CLI doesn't have a way to easily update this, and it'd be NICE if this was consistent across all platforms. On Mon, Jan 27, 2014 at 12:37 PM, Joe Bowser <[email protected]> wrote: > So, Android's versionCode has to be an integer: > > > On Mon, Jan 27, 2014 at 12:31 PM, Shazron <[email protected]> wrote: >> Commenting for iOS >> >> 1. n/a >> 2. Essentially for our purposes CFBundleVersion == >> CFBundleShortVersionString. CFBundleShortVersionString is usually a version >> number for marketing purposes (say major.minor), and CFBundleVersion is the >> "actual" internal build number, which may be of the longer form >> (major.minor.patch.build) >> 3. Sure >> >> >> On Mon, Jan 27, 2014 at 11:52 AM, Mark Koudritsky <[email protected]> wrote: >> >>> On Android and iOS there are two different values in project config for >>> setting version numbers. >>> >>> We are currently using the "version" attribute form config.xml to set >>> versionName on Android and CFBundleShortVersionString on iOS. The other >>> version values are not set (that is versionCode on Android and >>> CFBundleVersion on iOS are not set by cordova). >>> >>> 1. What about other platforms, which of them also have two different places >>> to set the version? >>> >>> 2. What's is typically used for CFBundleVersion on iOS? So far I've seen it >>> usually being set to the same value as CFBundleShortVersionString. Should >>> cordova-cli just do that? >>> >>> 3. I want to add a single value in config.xml file that could be used to >>> set the "other" versions for both Android and iOS. Does this sound >>> reasonable? >>>
