{ "id": "61990", "key": "TIMOB-1358", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11229", "name": "Release 1.5.0 M04", "archived": true, "released": true, "releaseDate": "2010-12-06" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:55:58.000+0000", "created": "2011-04-15T02:50:21.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "android", "feature" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:55:58.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}
Titanium.buildHash and Titanium.buildDate return null on\nandroid, return values on iOS.
\n[DST] Implementation Note: Log the\ninformation at the top of each builder.py run with our other\ndiagnostic information at the INFO level. This will make it easier\nto diagnose then going into the app.
site_scons/package.py builds version.txt and drops it into the\nmobilesdk/OS/VERSION dir. Then it looks like\nsupport/iphone/builder.py processes the file to make it available\nto the application.
Hey Bill, on iOS Titanium.buildDate returns the date in\nmm/dd/year, while on android its year/mm/dd - is it desirable or\nnecessary for these to return the same format? Other wise this is\nresolved.
wrong ticket for this comment, pls ignore
(from [385f47fb6c9f857e2b6e87e1d432242be84acf4b])\n[#1358] We were off-by-one when parsing the build\nhash \nhttp://github.com/appcelerator/titanium_mobile/commit/385f47fb6c9f8...
I never answered Thomas's earlier question. ... From my\nperspective it's fine as-is. I was using pre-existing code that we\nalready had for getting the hash, date, etc., and didn't see a need\nto re-invent the wheel. I mean it's certainly not the only thing\nthat is different between what users see when they build iPhone\nversus Android. I think it's okay, but if I'm out-voted, let me\nknow. :)
(from [9ad2e16bf5183ac47c90d9b7501eab7ab784b13c])\n[#1358] Also added display of the build version,\ntimestamp and hash at application startup, in the default uncaught\nhandler and the analytics event for exceptions \nhttp://github.com/appcelerator/titanium_mobile/commit/9ad2e16bf5183...
(from [1c05216249dc5a6025ecb0765df9ce023912cedd])\n[#1358] Also added display of the build version,\ntimestamp and hash at application startup, in the default uncaught\nhandler and the analytics event for exceptions \nhttp://github.com/appcelerator/titanium_mobile/commit/1c05216249dc5...
don, exec. decision req'd, see my October 1st, 2010 @ 04:37 PM\ncomment
don agreed with me that it's okay as-is. Okay with Thomas to\nclose?
Titanium SDK version: 1.5.0 (12/04/10 08:46 b7b9e78)