Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.1.0
-
None
-
None
-
OSX
Description
The version attribute from config.xml updates fields with different semantic in Android vs iOS.
Both platforms have 2 different version numbers. One acts as the "public" version number (published on the markets, etc) and the other acts as a "private" build number (changing with each development iteration)
The current behavior is:
- Android: updates the android:versionName ( A string value that represents the release version of the application code, as it should be shown to users )
- iOS: updates the CFBundleVersion instead: ( represents an iteration (released or unreleased) of the bundle and can contain a mix of characters and numbers, as in 12E123)
So, android updates the visible version, but iOS updates the private one.
This should be synced… I think it makes sense to have the config.xml version be the public one.
This means update the iOS tooling to fill the CFBundleShortVersionString instead.
That way, CFBundleVersion and android:versionCode remain "private versions", maybe using the build number from a continous integration server…
Attachments
Attachments
Issue Links
- relates to
-
CB-5093 CLI builds version number inconsitently between iOS and Android
- Closed