[TIMOB-14009] Android Emulator Debugger: Breakpoints are not getting hit for alloy project
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Critical |
|---|
| Status | Closed |
|---|
| Resolution | Cannot Reproduce |
|---|
| Resolution Date | 2013-05-28T20:48:28.000+0000 |
|---|
| Affected Version/s | Release 3.1.1 |
|---|
| Fix Version/s | n/a |
|---|
| Components | Android |
|---|
| Labels | qe-3.1.1 |
|---|
| Reporter | Deepti Pandey |
|---|
| Assignee | Ingo Muschenetz |
|---|
| Created | 2013-05-24T13:32:48.000+0000 |
|---|
| Updated | 2014-06-18T10:50:05.000+0000 |
|---|
Description
Test Steps:
1. Create an alloy mobile project ( supported to iOS , Android platform)
2. Add an alert in app.js file and set a breakpoint over it.
3. Launch the alloy project to 'Debug with android emulator'
Actual result:
Alert is shown on the emulator but breakpoint is not getting hit.
logs attached.
Attachments
I am unable to reproduce this issue. I used the default Alloy project app/controllers/index.js: line 2 (alert()). Appcelerator Studio 3.1.1.201305271814: Mountain Lion 10.8.3 Android SDK Tools: r22.0.1 Android Emulator: Google APIs 2.3.3 Titanium SDK: 3.1.1.v20130524180421 Titanium CLI: 3.1.1-alpha Titanium Alloy: 1.1.3-alpha Node.js: v0.8.22 NPM: 1.2.14 Note: Alloy projects do not have an exposed app.js file.
If you see this again, please include a full environment, exact reproduction steps, with sample code, file paths, and demarcated breakpoints. Logs to include: studio log w/troubleshooting debug => all studio diagnostic log ti info android tools version debug log located in /workspace/.metadata/.plugins/com.appcelerator.titanium.mobile/logs
Resolving as Cannot Reproduce.
Closing this issue as Not Reproducible using : Mac :10.9.3 Appcelerator Studio, build: 3.3.0.201406111952 SDK 3.3.0.v20140617161713 acs-1.0.14 alloy@1.4.0-rc npm-1.3.2 titanium@3.3.0-rc titanium-code-processor-1.1.1 Hence closing as NOT Repoducible ticket. Breakpoint is getting hit on emulator.