{ "id": "111486", "key": "AC-2492", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12217", "key": "AC", "name": "Appcelerator - INBOX", "projectCategory": { "id": "10000", "description": "", "name": "Customer Service" } }, "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2013-04-01T16:49:05.000+0000", "created": "2013-03-21T07:35:14.000+0000", "labels": [ "regression", "triage" ], "versions": [], "issuelinks": [ { "id": "27865", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "outwardIssue": { "id": "112224", "key": "TIMOB-13388", "fields": { "summary": "CLI: RangeError: Maximum call stack size exceeded", "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" } }, "priority": { "name": "High", "id": "2" }, "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } } ], "assignee": { "name": "dsefton", "key": "dsefton", "displayName": "Daniel Sefton", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2016-03-08T07:41:32.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": [], "description": "h3. Steps to Reproduce\r\nOn Mac 10.8.2, I installed titanium with 2 different sdks (3.0.2, 3.0.0) and whenever I try to run anything on the iphone simulator, even the sample files, I get an error.\r\n\r\nEDIT: I just tried 2.1.4 again and it worked this time. \r\n\r\nh3. Actual Result\r\nThe error is:\r\n/usr/local/lib/node_modules/titanium/node_modules/longjohn/index.js:114\r\n throw e;\r\n ^\r\nRangeError: Maximum call stack size exceeded\r\n\r\nh3. Expected Result\r\nPrograms should run in simulator.", "attachment": [ { "id": "36508", "filename": ".log", "author": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "created": "2013-03-21T07:35:16.000+0000", "size": 36200, "mimeType": "application/octet-stream; charset=ISO-8859-1" }, { "id": "36509", "filename": "diagnostic6768943843961921266.log", "author": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "created": "2013-03-21T07:35:18.000+0000", "size": 1494, "mimeType": "application/octet-stream; charset=ISO-8859-1" } ], "flagged": false, "summary": "iOS: RangeError: Maximum call stack size exceeded when running simulator", "creator": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "subtasks": [], "reporter": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "environment": "Titanium Studio 3.0.2\r\nTi SDK 3.0.2 GA, 3.0 GA\r\nOS X 10.8.2", "comment": { "comments": [ { "id": "243457", "author": { "name": "dsefton", "key": "dsefton", "displayName": "Daniel Sefton", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Hi Vic,\n\nDoes this happen for all the Studio template projects like \"Default Project\", and \"Default Alloy Project\" too?\n\nIs this a runtime, or build-time error?\n\nCheers.", "updateAuthor": { "name": "dsefton", "key": "dsefton", "displayName": "Daniel Sefton", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-03-21T18:00:42.000+0000", "updated": "2013-03-21T18:00:42.000+0000" }, { "id": "243516", "author": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Hello Vic,\r\n\r\nThe CLI (Command line interface) uses commands for things like \"build\" and \"clean\" that come from the SDK. Which SDK it uses for this purpose is set by the command \"ti sdk select\". To use the commands from 3.0.2.GA for example, you set \"ti sdk select 3.0.0.GA\". To see the setting you currently have, you can simply enter \"ti sdk\" in the terminal, and you should see the SDK set as \"active\". I recommend you set this to 3.0.2.GA in your case.\r\n\r\nThis is different than the SDK used to compile, which is set in the project's Tiapp.xml. While these could be different, it's a good idea to keep them in sync when possible.\r\n\r\nCould you report the version of npm and node you are running? \"npm -v\" and 'node -v\" in the terminal? Thanks.", "updateAuthor": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-03-21T20:22:31.000+0000", "updated": "2013-03-21T20:22:58.000+0000" }, { "id": "243527", "author": { "name": "silverag47", "key": "silverag47", "displayName": "geoff", "active": true, "timeZone": "America/New_York" }, "body": "Hi Eric,\nI'm having the same issue.\nI tried the latest nightly and updated node to 0.9.0 \nnpm is 1.1.44\n\nI'm about re-download 3.0.2 studio and re-install it.\n\nDaniel,\nI have managed to get the simulator with work via CLI but I cannot publish an iOS app via titanium studio nor the CLI. It looks like a build time error.\n", "updateAuthor": { "name": "silverag47", "key": "silverag47", "displayName": "geoff", "active": true, "timeZone": "America/New_York" }, "created": "2013-03-21T21:02:05.000+0000", "updated": "2013-03-21T21:02:05.000+0000" }, { "id": "243705", "author": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "body": "@Daniel Yes it happens for those templates as well. It might be a build time error, I'm not sure.\n\n@Eric I'll try that. Also npm version is 1.2.14 and node is v0.10.0", "updateAuthor": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "created": "2013-03-22T17:20:57.000+0000", "updated": "2013-03-22T17:20:57.000+0000" }, { "id": "243908", "author": { "name": "andreperazzi", "key": "andreperazzi", "displayName": "André Perazzi", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I'm having the same problem...\r\nsdks (3.0.2, 3.0.0) \r\nNpm v. 1.2.14\r\nNode v. v0.10.0\r\nTitanium Studio, build: 3.0.2.201302191606\r\nCLI version 3.0.24\r\n\r\n\r\n---------------------\r\nFixed the problem installing an older version of Node: v0.8.17", "updateAuthor": { "name": "andreperazzi", "key": "andreperazzi", "displayName": "André Perazzi", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-03-25T14:10:47.000+0000", "updated": "2013-03-25T14:19:08.000+0000" }, { "id": "243910", "author": { "name": "silverag47", "key": "silverag47", "displayName": "geoff", "active": true, "timeZone": "America/New_York" }, "body": "I fixed my issue, somehow the project itself was corrupted.\n@Vic and @Andre\nYou need to uninstall your node.js You are using version 0.10.0 which is not supported. I recommend downloading version 0.8.17. Here is a link to that version: http://nodejs.org/dist/v0.8.17/ ", "updateAuthor": { "name": "silverag47", "key": "silverag47", "displayName": "geoff", "active": true, "timeZone": "America/New_York" }, "created": "2013-03-25T14:15:30.000+0000", "updated": "2013-03-25T14:15:30.000+0000" }, { "id": "244071", "author": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "body": "@geoff that fixed it. Thanks!", "updateAuthor": { "name": "fchaos", "key": "fchaos", "displayName": "Vic Agu", "active": true, "timeZone": "America/Chicago" }, "created": "2013-03-26T02:59:04.000+0000", "updated": "2013-03-26T02:59:04.000+0000" }, { "id": "244910", "author": { "name": "dsefton", "key": "dsefton", "displayName": "Daniel Sefton", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I'm going to assume that installing the supported version of node.js is the fix for this issue. Resolving.", "updateAuthor": { "name": "dsefton", "key": "dsefton", "displayName": "Daniel Sefton", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-04-01T16:49:05.000+0000", "updated": "2013-04-01T16:49:05.000+0000" }, { "id": "244911", "author": { "name": "andreperazzi", "key": "andreperazzi", "displayName": "André Perazzi", "active": true, "timeZone": "America/Los_Angeles" }, "body": "It fixes.", "updateAuthor": { "name": "andreperazzi", "key": "andreperazzi", "displayName": "André Perazzi", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-04-01T16:52:11.000+0000", "updated": "2013-04-01T16:52:30.000+0000" }, { "id": "269227", "author": { "name": "neosergio", "key": "neosergio", "displayName": "Sergio Infante Montero", "active": true, "timeZone": "America/Bogota" }, "body": "I have the same issue with iOS simulator, and I have v0.8.17 version for node. The problem is not solved", "updateAuthor": { "name": "neosergio", "key": "neosergio", "displayName": "Sergio Infante Montero", "active": true, "timeZone": "America/Bogota" }, "created": "2013-09-02T17:31:02.000+0000", "updated": "2013-09-02T17:31:02.000+0000" } ], "maxResults": 10, "total": 10, "startAt": 0 } } }