{ "id": "141843", "key": "TIMOB-18257", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "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": [], "resolution": { "id": "5", "description": "All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.", "name": "Cannot Reproduce" }, "resolutiondate": "2019-08-13T17:24:41.000+0000", "created": "2014-12-18T06:22:03.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "engTriage", "qe-3.5.0", "regression" ], "versions": [ { "id": "16704", "description": "Release 3.5.0", "name": "Release 3.5.0", "archived": false, "released": true, "releaseDate": "2015-01-13" } ], "issuelinks": [], "assignee": { "name": "cwilliams", "key": "cwilliams", "displayName": "Christopher Williams", "active": true, "timeZone": "America/New_York" }, "updated": "2019-08-13T17:24:47.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": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "This is a Regression as the issue does not occur with 3.4.1.GA SDK.\r\n\r\nThe issue happens on both iOS and Android for Alloy project. For Classic project it works fine.\r\n\r\nSteps to Reproduce:\r\n1. Create a default alloy project and add following code to index.js\r\n{code}\r\nfunction doClick(e) {\r\n alert($.label.text);\r\n Ti.API.info(\"Testing Debug\");\r\n}\r\n$.index.open();\r\n{code}\r\n2. Put a breakpoint at line 2\r\n3. Debug the project for iOS device. In the app click on the label\r\nThe breakpoint at line 2 is hit\r\n4. Click on Step Over or Step Into. The alert is shown in the app and the debug execution now suspends at line 3.\r\n5. Again click on Step Over or Step Into. The console shows the info \"Testing Debug\"\r\n\r\nActual Result:\r\nThe debugger still remains suspended at line 3 instead of finishing. Clicking again on Step Over or Step Into finishes the debug execution. (i.e. we need to perform Step Over twice on the last line).", "attachment": [], "flagged": false, "summary": "Debugger: In Alloy project, the debugger hits the last line of code twice in Step Over and Step Into", "creator": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "SDK: 3.5.0.v20141217170926\r\nStudio: 3.4.1.201410281743\r\nCLI: 3.4.1\r\nAlloy: 1.5.1\r\nOS: Mac OSX 10.10.1", "closedSprints": [ { "id": 1160, "state": "closed", "name": "2019 Sprint 17", "startDate": "2019-08-12T07:59:28.950Z", "endDate": "2019-08-25T07:59:00.000Z", "completeDate": "2019-08-26T15:35:29.980Z", "originBoardId": 114 } ], "comment": { "comments": [ { "id": "337034", "author": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "body": "This comment\r\n{quote}\r\nThe issue happens on both iOS and Android for Alloy project. For Classic project it works fine\r\n{quote}\r\nThe fact that this happens on Android as well, which has not been changes, makes me think that this is not a debugger issue, but an Alloy issue.", "updateAuthor": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2014-12-18T19:12:23.000+0000", "updated": "2014-12-18T19:12:23.000+0000" }, { "id": "337051", "author": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "body": "While I can confirm the behavior described in this ticket, Alloy has not changed for 3.5.0. We're shipping 1.5.1 with both SDK 3.4.1.GA and 3.5.0. Besides, all Alloy does is create the source map files used by Studio to enable the actual debugging. I'm not sure how this could be an Alloy issue.", "updateAuthor": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "created": "2014-12-18T21:16:27.000+0000", "updated": "2014-12-18T21:16:27.000+0000" }, { "id": "337062", "author": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Investigating", "updateAuthor": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2014-12-18T21:56:55.000+0000", "updated": "2014-12-18T21:56:55.000+0000" }, { "id": "337066", "author": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Ah! this is actually intended, even if this feature did not exist in the older debugger. \r\nThis \"pause reason\" is called \"beforeReturn\", and this allows you to inspect the all variables of that function, even if there is a variable declaration at the very last line of the function body.\r\n\r\nI have removed this feature from iOS to make it work like it did back in 3.4.x", "updateAuthor": { "name": "penrique", "key": "penrique", "displayName": "Pedro Enrique", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2014-12-18T22:10:14.000+0000", "updated": "2014-12-18T22:10:58.000+0000" }, { "id": "337205", "author": { "name": "fcasali", "key": "fcasali", "displayName": "Federico Casali", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Tested on iOS (iPhone 6 + , iOS 8.1)\r\nI could reproduce the issue but noticed a slight difference between first launch and subsequent ones.\r\n\r\nRefer to the code in the bug description:\r\n\r\n1. launch\r\na. click on the label \r\nResult: breakpoint at line 2 is hit\r\nb. click on StepInto or StepOver \r\nResult: execution stops at line 3 (and alert is displayed)\r\nc. click on StepInto or StepOver again \r\nResult: execution is still stopped at line 3 (no alert is displayed)\r\nd. click once again StepIinto or StepOver\r\nResult: execution ends, therefore as reported in the bug, a further step clicking on stepInto or stepOver is required\r\n\r\n2. Subsequent runs behave in this way:\r\na. click on the label\r\nResult: execution stops, but this time it stops at line 1, on the function() \r\nb. click on StepInto or StepOver \r\nResult: execution stops now at line 2\r\nc. click on StepInto or StepOver again\r\nResult: execution now stops at line 3 and alert is displayed\r\nd. click once again StepIinto or StepOver\r\nResult: Result: execution ends, therefore as reported in the bug, a further step clicking on stepInto or stepOver is required", "updateAuthor": { "name": "fcasali", "key": "fcasali", "displayName": "Federico Casali", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-12-19T19:57:05.000+0000", "updated": "2014-12-19T19:57:05.000+0000" }, { "id": "351579", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "Reopening ticket, using:\r\n\r\nMac OSX 10.10.3\r\nAppc Studio: 4.0.1.201505020103\r\nTitanium SDK build: 4.0.0.v20150430090209\r\nAppc CLI (NPM): 0.3.55\r\nAppc CLI (Registry): 0.2.279\r\n\r\nUsing the code in the description with the following line numbers\r\n\r\n{code}\r\n1 function doClick(e) {\r\n2 alert($.label.text);\r\n3 Ti.API.info(\"Testing Debug\");\r\n4 }\r\n5 $.index.open();\r\n{code}\r\n\r\nAs per Federicos comment I see the following behavior in the following scenarios:\r\n\r\nh3.First attempt\r\n\r\n1. Launch the app\r\n2. Press 'Hello, World' label on the app - *execution stops at line 2*\r\n3. Click on Step Into or Step Over - *Alert is shown, execution stops at line 3*\r\n4. Click on Step Into or Step Over - *Execution stays stopped at line 3*\r\n5. Click on Step Into or Step Over - *Debugging stops*\r\n\r\nh3.Subsequent attempts\r\n\r\n1. Press 'Hello, World' label on the app - *execution stops at line 1*\r\n2. Click on Step Into or Step Over - *Execution stops at line 2*\r\n3. Click on Step Into or Step Over - *Alert is shown, execution stops at line 3*\r\n4. Click on Step Into or Step Over - *Execution stays stopped at line 3*\r\n5. Click on Step Into or Step Over - *Debugging stops*", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2015-05-04T20:32:33.000+0000", "updated": "2015-05-04T20:32:33.000+0000" }, { "id": "450448", "author": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "body": "The issue is no more reproducible with the latest builds.\r\nThe debug execution does not remain suspended on the same line, if not relevant, after step into or step over.\r\nVerified on:\r\nMac OS 10.14.6\r\nTi SDK: 8.1.0.v20190812112926\r\nAppc CLI: 7.1.0\r\nNode: 10.5.0\r\nJDK: 10.0.2\r\nXcode: 10.3\r\nStudio: 5.1.3.201907112159\r\n\r\nHence closing the issue.", "updateAuthor": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2019-08-13T17:21:03.000+0000", "updated": "2019-08-13T17:21:03.000+0000" } ], "maxResults": 10, "total": 10, "startAt": 0 } } }