cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Вячеслав Шабельник (JIRA) <>
Subject [jira] [Commented] (CB-5093) CLI builds version number inconsitently between iOS and Android
Date Mon, 23 Dec 2013 16:55:53 GMT


Вячеслав Шабельник commented on CB-5093:

Hi! I also have this trouble and this is big shame. I ask guys from cordova - please be so
kind and review and add my fix to next release! Here it is:

> CLI builds version number inconsitently between iOS and Android
> ---------------------------------------------------------------
>                 Key: CB-5093
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android, CLI, iOS
>    Affects Versions: 3.1.0
>            Reporter: Adam George
>            Assignee: Braden Shepherdson
> I'm hoping this issue isn't just my ignorance, but I'm finding the app version number
generation via the CLI to be inconsistent and odd.
> iOS and Android both support a version number (which is what is displayed in the app
stores), as well as another string, which most people use as a build number.
> E.g. for iOS:
> Myapp-Info.plist:
> Bundle versions string, short:   1.0.0     (this is what will show in the app store)
> Bundle version:  0.0.3    (this is some other build number)
> Android:
> AndroidManifest.xml:
> android:versionCode="1" android:versionName="0.0.3"
> versionName is what shows in the stores, and versionCode is typically used like a build
number (as far as I can tell).
> My point is, in the cordova.xml, I only have the ability to set one of these version
numbers.  There is only a single "version" attribute.
> But we need two attributes, so we can set both version strings via the CLI.
> Secondly, how the "version" attribute is applied when building via the CLI is inconsistent.
 On iOS it's updating the "build" number, and not even touching the main version number that
users will see in the store.
> Whereas Android has what I would expect as the correct behaviour.
> Anyway, please let me know if I've misunderstood anything.

This message was sent by Atlassian JIRA

View raw message