Titanium JIRA Archive
Alloy (ALOY)

[ALOY-1650] Debugger does not hit breakpoints when running Android on Windows

GitHub Issuen/a
Resolution Date2019-03-14T14:52:27.000+0000
Affected Version/sAlloy 1.13.8
Fix Version/sCLI Release 7.0.10
ReporterSamir Mohammed
AssigneeEwan Harris


*Note:* _When using alloy 1.13.7 no issue can be seen but when using 1.13.8 the debugger does not work 1.13.8 can be found in 7.0.10-master.14. Titanium apps don't see this issue._ When trying to debug an Android application in Windows, the debugger does not work and seems to miss breakpoints. *Test Steps*

Create an alloy application

Set some break points in the index.js

Set the Studio drop down menu to debug (next to green play button)

Press the green play button

Wait for application to build an run

*Expected result* Debugger should work and hit breakpoints. *Actual result* Debugger does not work at all.


  1. Ewan Harris 2019-03-13

    Working with Samir we can see the following * ALOY-1644 is definitely the cause of this * Specifically [this line](https://github.com/appcelerator/alloy/blob/784c0a7ea45510953533b1748dae0407316434b8/Alloy/commands/compile/index.js#L1158) is causing the issue as it appears that my change to normalize the path into windows style clashes with the constructed regex using posix path separator. The fix here looks to be to roll back that specific line, but we need to be sure that doesn't cause ALOY-1644 again.
  2. Ewan Harris 2019-03-13

  3. Samir Mohammed 2019-03-14

    *Closing ticket.* Fix verified in CLI version 7.0.10-master.18. Able to use the debugger without major issues and still able to use liveview without any issues. Also used SDK version 8.0.0.v20190311082612 and Appc Studio Version

JSON Source