{ "id": "170643", "key": "ALOY-1606", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "11113", "key": "ALOY", "name": "Alloy", "projectCategory": { "id": "10400", "description": "Tools for developing applications", "name": "Tooling" } }, "fixVersions": [ { "id": "20064", "name": "CLI Release 7.0.3", "archived": false, "released": true } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2018-03-29T15:35:06.000+0000", "created": "2017-12-18T20:18:03.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "updated": "2018-05-02T10:23:10.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": "Breakpoints are not being hit when using the debugger and when trying to debug to device the following error is shown:\r\n\r\n{code:java}\r\n[WARN] : TiApplication: (main) [57,57] Registering module with name already in use.\r\n[WARN] : JSDebugger: (main) [20,77] Debugger listening on ws://127.0.0.1:56603/07e088ff-53f1-476c-a9a2-58a8cd6016b0\r\n[WARN] : JSDebugger: (main) [0,77] To connect Chrome DevTools, open Chrome to chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:56603/07e088ff-53f1-476c-a9a2-58a8cd6016b0\r\n[WARN] : JSDebugger: (main) [0,77] Waiting for debugger to connect for next 60 seconds...\r\n[ERROR] : JSDebugger: (WebsocketSelector1939) [2,79] Error with websocket server\r\n[ERROR] : JSDebugger: java.net.BindException: Address already in use\r\n[ERROR] : JSDebugger: at sun.nio.ch.Net.bind0(Native Method)\r\n[ERROR] : JSDebugger: at sun.nio.ch.Net.bind(Net.java:442)\r\n[ERROR] : JSDebugger: at sun.nio.ch.Net.bind(Net.java:434)\r\n[ERROR] : JSDebugger: at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:224)\r\n[ERROR] : JSDebugger: at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)\r\n[ERROR] : JSDebugger: at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)\r\n[ERROR] : JSDebugger: at org.java_websocket.server.WebSocketServer.run(WebSocketServer.java:296)\r\n[ERROR] : JSDebugger: at java.lang.Thread.run(Thread.java:764)\r\n{code}\r\n\r\n*Test steps:*\r\n+ Create an alloy project with all modules enabled\r\n+ go to {{app/controllers/app.js}}\r\n+ Set breakpoints on line 2 and 5\r\n+ Press the debug button from the selection menu \r\n+ Run the program to an emulator \r\n+ When program launches breakpoints are not hit and user is able to click \"Hello world\" without the break point getting hit\r\n+ Now debug the application for a device \r\n+ Studio shows the above error \r\n\r\n*Expected result:*\r\nDebugger should be able to hit breakpoints and no error should be shown when debugging to device\r\n", "attachment": [ { "id": "63837", "filename": "index.js", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2017-12-19T13:05:45.000+0000", "size": 63, "mimeType": "application/javascript" }, { "id": "63836", "filename": "index.js", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2017-12-19T13:04:05.000+0000", "size": 1398, "mimeType": "application/javascript" }, { "id": "63833", "filename": "Screen Shot 2017-12-19 at 2.40.39 PM.png", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2017-12-19T06:56:41.000+0000", "size": 1824151, "mimeType": "image/png" }, { "id": "63834", "filename": "Screen Shot 2017-12-19 at 2.42.51 PM.png", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2017-12-19T06:56:56.000+0000", "size": 431514, "mimeType": "image/png" } ], "flagged": false, "summary": "Android: Debugger not hitting breakpoints on Windows", "creator": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "Operating System:\r\n Name = Microsoft Windows 10 Pro\r\n Version = 10.0.15063\r\n Architecture = 64bit\r\n CPUs = 4\r\n Memory = 16.0GB\r\n\r\nNode.js\r\nNode.js Version: 8.9.1\r\nnpm Version: 5.4.2\r\n\r\nAppcelerator CLI\r\nInstaller: 4.2.11\r\nCore Package: 7.0.1-master.5\r\n\r\nTitanium CLI\r\nCLI Version: 5.0.14\r\nnode-appc Version: 0.2.41\r\n\r\nTitanium SDK: 7.0.1.v20171218094049\r\nAppc Studio version: 5.0.0.201712081732 (GA)", "comment": { "comments": [ { "id": "432311", "author": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "body": "When I disabled SOASTA I no longer received the above error on the Android device however breakpoints were still not getting hit. ", "updateAuthor": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2017-12-18T21:17:23.000+0000", "updated": "2017-12-18T21:17:23.000+0000" }, { "id": "432320", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "[~smohammed] I got the error with an application that did not have soasta\r\n\r\n\r\n{noformat}\r\n-- Start application log -----------------------------------------------------\r\n[INFO] : TiApplication: (main) [0,0] checkpoint, app created.\r\n[INFO] : TiApplication: (main) [31,31] Titanium 7.0.1 (2017/12/18 09:41 undefined)\r\n[INFO] : MultiDex: VM with version 2.1.0 has multidex support\r\n[INFO] : MultiDex: install\r\n[INFO] : MultiDex: VM has multidex support, MultiDex support library is disabled.\r\n[INFO] : Project built successfully in 39s 978ms\r\n[WARN] : TiAndroid: (main) [1004,1035] Application instance no longer available. Unable to get current activity.\r\n[WARN] : TiAndroid: (main) [1,1036] Application instance no longer available. Unable to get current activity.\r\n[WARN] : TiAndroid: (main) [0,1036] Application instance no longer available. Unable to get current activity.\r\n[WARN] : JSDebugger: (main) [30,1066] Debugger listening on ws://127.0.0.1:62092/107384af-9e3b-4a84-9661-ef847f8e4e26\r\n[WARN] : JSDebugger: (main) [0,1066] To connect Chrome DevTools, open Chrome to chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:62092/107384af-9e3b-4a84-9661-ef847f8e4e26\r\n[WARN] : JSDebugger: (main) [0,1066] Waiting for debugger to connect for next 60 seconds...\r\n[WARN] : JSDebugger: (WebSocketWorker-19368) [303,1369] Debugger client connected\r\n[INFO] : TiApplication: (main) [113,1482] Titanium Javascript runtime: v8\r\n[INFO] : TiRootActivity: (main) [0,0] checkpoint, on root activity create, savedInstanceState: null\r\n[WARN] : TiApplication: (main) [62,62] Registering module with name already in use.\r\n[WARN] : JSDebugger: (main) [16,78] Debugger listening on ws://127.0.0.1:62092/56a6f667-673a-4ee8-bb72-9baa6e56470e\r\n[WARN] : JSDebugger: (main) [1,79] To connect Chrome DevTools, open Chrome to chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:62092/56a6f667-673a-4ee8-bb72-9baa6e56470e\r\n[WARN] : JSDebugger: (main) [0,79] Waiting for debugger to connect for next 60 seconds...\r\n[ERROR] : JSDebugger: (WebsocketSelector19392) [0,79] Error with websocket server\r\n[ERROR] : JSDebugger: java.net.BindException: Address already in use\r\n[ERROR] : JSDebugger: \tat sun.nio.ch.Net.bind0(Native Method)\r\n[ERROR] : JSDebugger: \tat sun.nio.ch.Net.bind(Net.java:442)\r\n[ERROR] : JSDebugger: \tat sun.nio.ch.Net.bind(Net.java:434)\r\n[ERROR] : JSDebugger: \tat sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:224)\r\n[ERROR] : JSDebugger: \tat sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)\r\n[ERROR] : JSDebugger: \tat sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)\r\n[ERROR] : JSDebugger: \tat org.java_websocket.server.WebSocketServer.run(WebSocketServer.java:296)\r\n[ERROR] : JSDebugger: \tat java.lang.Thread.run(Thread.java:764)\r\n[WARN] : JSDebugger: (WebSocketWorker-19369) [41050,41129] Debugger client connected\r\n{noformat}\r\n", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2017-12-18T21:42:58.000+0000", "updated": "2017-12-18T21:43:21.000+0000" }, { "id": "432376", "author": { "name": "amukherjee", "key": "amukherjee", "displayName": "Abir Mukherjee", "active": true, "timeZone": "America/Los_Angeles" }, "body": "This same issue is also seen on Mac-Android.", "updateAuthor": { "name": "amukherjee", "key": "amukherjee", "displayName": "Abir Mukherjee", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2017-12-19T00:07:35.000+0000", "updated": "2017-12-19T00:07:35.000+0000" }, { "id": "432380", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "Verified the same use case on MacOS HighSierra 10.13.2 (17C88) and can confirm that it is working fine (all the desired breakpoints are hit) using Android device and Android Genymotion emulators.\r\nAlso tested this against iOS devices and iOS simulators, and no issue has been observed. \r\n\r\n*Screenshots*:\r\n !Screen Shot 2017-12-19 at 2.40.39 PM.png|thumbnail! \r\n&\r\n !Screen Shot 2017-12-19 at 2.42.51 PM.png|thumbnail! \r\n\r\n*Environment*:\r\n*_CLI_* - 7.0.1-master.5\r\n*_Ti SDK_*: 7.0.1.v20171218094049 [\r\n*_Node_*: v8.9.1\r\n\r\n\r\nWill also check this out on Windows and update this thread.", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2017-12-19T06:58:25.000+0000", "updated": "2017-12-19T06:58:25.000+0000" }, { "id": "432393", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "Verified this on Windows 10, and I could reproduce the issue using Genymotion and Android emulators (had some issue with Pixel 2 XL device's app install though, unrelated to Titanium).\r\n\r\n[~cwilliams], I noticed that the mapping for Android is not properly being generated (Please check the attached files and below log statements for reference).\r\nSince we haven't modified anything on Android V8 inspector and Android debugger path within Studio code base, could this be a problem with babble or some underlying map generator? Please advice.\r\n\r\nGenerated index.js --> [^index.js] \r\nActual index.js --> [^index.js] \r\n\r\n{quote}!ENTRY com.aptana.debug.core 1 0 2017-12-19 20:55:27.083\r\n!MESSAGE (Build 5.0.0.201712081732) [INFO] com.aptana.debug.core/debugger_debug *_Generated mapping while adding breakpoint for L/alyMobApp1/app/controllers/index.js:2 is Resources/android/alloy/controllers/index.js:55_*\r\n\r\n!ENTRY com.aptana.debug.core 1 0 2017-12-19 20:55:27.208\r\n!MESSAGE (Build 5.0.0.201712081732) [INFO] com.aptana.debug.core/debug [^index.js] ger_debug *_Generated mapping while adding breakpoint for L/alyMobApp1/app/controllers/index.js:5 is Resources/android/alloy/controllers/index.js:58_*{quote}\r\n\r\n*Edit:* \r\nLine numbers 55 and 58 are non existing in the generated index.js. ", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2017-12-19T13:07:37.000+0000", "updated": "2017-12-19T13:11:19.000+0000" }, { "id": "432750", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "Corrected title as it works fine for Mac, especially after TISTUD-8966 fix. ", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-01-04T16:52:28.000+0000", "updated": "2018-01-04T16:52:28.000+0000" }, { "id": "434226", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "*Update*: \r\nAnalysed this scenario both on Mac and Windows environment. Noticed that its the mapping file (path: *_/build/map/Resources/android/alloy/controllers/index.js.map_*) which seems to have been generated wrongly. \r\nThe map file is being generated as part of build process (probably CLI is building this). We would need SDK/CLI team to take a look at this scenario on windows. ", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-02-08T05:17:14.000+0000", "updated": "2018-02-08T05:17:14.000+0000" }, { "id": "434730", "author": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "body": "PR: https://github.com/appcelerator/alloy/pull/880", "updateAuthor": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "created": "2018-02-21T20:57:43.000+0000", "updated": "2018-02-21T20:57:43.000+0000" }, { "id": "436094", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "For verification be wary that I was unable to see the source when the breakpoint was hit, I filed TISTUD-9049 as this occurs for both classic and alloy apps", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2018-03-29T15:37:15.000+0000", "updated": "2018-03-29T15:37:15.000+0000" }, { "id": "437258", "author": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Closing ticket,\r\nVerified in cli version 7.0.3-master.39\r\n", "updateAuthor": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-05-01T18:04:50.000+0000", "updated": "2018-05-01T18:04:50.000+0000" }, { "id": "437259", "author": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "updateAuthor": { "name": "smohammed", "key": "smohammed", "displayName": "Samir Mohammed", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-05-01T18:05:51.000+0000", "updated": "2018-05-01T18:05:51.000+0000" }, { "id": "437279", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "Tried verifying this using latest studio (also using 5.0 GA Studio), on build 7.0.3-master.39, on a Mac. \r\nBreakpoint data isn't being returned correctly, there by causing the Studio to ignore the breakpoints set by using in Studio (for both device and simulators)\r\nThe prior versions of CLI had no issue with this data on Mac. \r\nI am yet to verify this on Windows (to see if I encounter TISTUD-9049).", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-05-02T10:23:10.000+0000", "updated": "2018-05-02T10:23:10.000+0000" } ], "maxResults": 14, "total": 14, "startAt": 0 } } }