[TIMOB-6541] Android: Debugger - (V8) Breakpoint condition with failures does not hit breakpoint and does not generate error
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2020-01-09T19:35:01.000+0000 |
| Affected Version/s | Release 1.8.0.1 |
| Fix Version/s | n/a |
| Components | Android |
| Labels | branch-v8, tbs-1.8.2 |
| Reporter | Wilson Luu |
| Assignee | Unknown |
| Created | 2011-12-09T12:02:55.000+0000 |
| Updated | 2020-01-09T19:35:01.000+0000 |
Description
Steps to reproduce:
1. Create a new Titanium mobile project and copy the following code to app.js
for (var i = 0; i < 10; i++) {
Ti.API.debug("Hello: " + i);
}
i ==
7. Run in debug
Actual: App is fully deployed and debugger does not hit breakpoint or generate error for bad breakpoint condition.
Expected: Debugger should hit breakpoint and generate error for bad breakpoint condition.
On both Windows 7 and Lion, breakpoint was hit, but no error was printed out to the console.
Had seen same issue. Breakpoint was not hit and there wan no error printed in console. Tested. Test Environment: Appc-Studio: 3.4.1 GA Titanium SDK: 3.5.0.v20141217170926 Titanium CLI: 3.4.1 GA Alloy : 1.5.1 GA OS: Windows 8.1 (x64) Device - Galaxy S5 (v4.4.2)
It has been decided that this issue should be closed as “Won’t do.” This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.