[TIMOB-12092] Info.plist : The CFBundleVersion key does not meet apple spec.
GitHub Issue | n/a |
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2013-04-08T11:32:43.000+0000 |
Affected Version/s | Release 2.1.4, Release 3.0.0 |
Fix Version/s | Release 3.0.2 |
Components | iOS |
Labels | n/a |
Reporter | Lokesh Choudhary |
Assignee | jithinpv |
Created | 2012-12-13T22:32:17.000+0000 |
Updated | 2017-03-21T21:58:09.000+0000 |
Description
Not a regression.
Description:
1.Take note of the version no on tiapp.xml(2.1.4GA).
Note:You can also use a four segment such as 1.2.3.4
2.Build kitchensink for iOS.
3.Open the info.plist file for kitchensink.
4.Notice the CFBundle version key in info.plist
Note:
CFBundleVersion (String - iOS, OS X) specifies the build version number of the bundle, which identifies an iteration (released or unreleased) of the bundle. The build version number should be a string comprised of three non-negative, period-separated integers with the first integer being greater than zero. The string should only contain numeric (0-9) and period (.) characters. Leading zeros are truncated from each integer and will be ignored (that is, 1.02.3 is equavalent to 1.2.3). This key is not localizable.
Actual Result:
1.You will see alpha characters next to the version number or four integers.
Expected Results:
1.You should just see max of 3 integers separated with periods.
Attachments
Issue does not reproduces Tested with Titanium Studio, build: 3.0.1.201212181159 Titanium SDK version: 3.1.0 Titanium SDK version: 3.0.2 iOS iPhone Simulator: iOS SDK version: 6.0
Issue does not reproduces Tested with iOS SDK: 5.1 iOS iPhone Simulator: 5.1 Mac OS X Version 10.7.5 Titanium SDK version 3.1.1.v20130606121419 Titanium Studio, build: 3.0.1.201212181159
just happend to us as well, on SDK 3.1.3.GA, we tried to get version 1.0.4.1 to build. we saw the .plist file in the resources folder which was fine, but the .plist filed copied by Titanium build process to the build folder was truncated
Closing ticket as the issue cannot be reproduced and due to the above comments.