[TIMOB-14893] CLI: When building, receive error: TypeError: Object # has no method 'get'
GitHub Issue
n/a
Type
Bug
Priority
Low
Status
Closed
Resolution
Won't Fix
Resolution Date
2013-08-19T16:31:01.000+0000
Affected Version/s
Release 3.2.0
Fix Version/s
n/a
Components
CLI
Labels
android, cli, ios, triage
Reporter
Adam Fennell
Assignee
Chris Barber
Created
2013-08-15T19:11:48.000+0000
Updated
2017-03-22T23:02:10.000+0000
Description
I can successfully build using Ti SDK versions upto and including 3.2.0.v20130730132443, for emulator or device, targeting iOS or Android.
However, when I try using any more recent SDK versions (e.g. 3.2.0.v20130814111647), the CLI build fails immediately with the following red text in the console:
[ERROR] : TypeError: Object #
Comments
Daniel Sefton 2013-08-15
I've also been getting this, but only for Alloy projects. Escalating now.
Adam Fennell 2013-08-16
This project is an Alloy v1.1 app.
After upgrading today to Alloy 1.2 & CLI 3.1.2, this issue still occurs exactly as described.
Adam Fennell 2013-08-19
I know there's only been 1 business day gone (at best) since this issue was raised, so please excuse the question. I'd like to know what the estimated turnaround of issues are, on average. This will help me know whether to hold out for future releases before publishing our app. An answer along the lines of a week, couple of weeks, a month, a couple of months, would be great. Thanks in advance.
Chris Barber 2013-08-19
If you want to use a 3.2.0 unstable SDK, then you need to upgrade to the latest 3.2.0 unstable Titanium CLI.
[~egomez] Titanium CLI requires node-appc 0.2 which is not published yet. Until node-appc 0.2.0 is published, or we setup CI builds, you'll need to manually clone the "titanium" git repo and manually update package.json, run npm install, and manually pull node-appc master from git.
On a side note, not sure why your comment was attached to this ticket. It doesn't appear to relate.
Eduardo Gomez 2013-08-29
Thanks, [~cbarber].
The reason to ask here was because a couple of developers were getting: "TypeError: Object # has no method 'get'" when building on 3.2 CI.
In regards with node-appc 0.2, I was wondering is there a time frame for publishing it?
Chris Barber 2013-08-29
node-appc 0.2 will ship when 3.2 ships. We may have CI builds of Titanium CLI which would include the latest node-appc before 3.2 ships.
I've also been getting this, but only for Alloy projects. Escalating now.
This project is an Alloy v1.1 app. After upgrading today to Alloy 1.2 & CLI 3.1.2, this issue still occurs exactly as described.
I know there's only been 1 business day gone (at best) since this issue was raised, so please excuse the question. I'd like to know what the estimated turnaround of issues are, on average. This will help me know whether to hold out for future releases before publishing our app. An answer along the lines of a week, couple of weeks, a month, a couple of months, would be great. Thanks in advance.
If you want to use a 3.2.0 unstable SDK, then you need to upgrade to the latest 3.2.0 unstable Titanium CLI.
Hi [~cbarber], a developer wants to use 3.2.0 and gets the following errors:
Please advise.[~egomez] Titanium CLI requires node-appc 0.2 which is not published yet. Until node-appc 0.2.0 is published, or we setup CI builds, you'll need to manually clone the "titanium" git repo and manually update package.json, run npm install, and manually pull node-appc master from git. On a side note, not sure why your comment was attached to this ticket. It doesn't appear to relate.
Thanks, [~cbarber]. The reason to ask here was because a couple of developers were getting: "TypeError: Object # has no method 'get'" when building on 3.2 CI. In regards with node-appc 0.2, I was wondering is there a time frame for publishing it?
node-appc 0.2 will ship when 3.2 ships. We may have CI builds of Titanium CLI which would include the latest node-appc before 3.2 ships.
Closing ticket as "Won't Fix".