[TIMOB-20503] debugging not working for IOS or Android on my machine
GitHub Issue | n/a |
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Done |
Resolution Date | 2018-03-27T09:02:00.000+0000 |
Affected Version/s | Release 5.2.0 |
Fix Version/s | n/a |
Components | n/a |
Labels | n/a |
Reporter | Michael Kellogg |
Assignee | Unknown |
Created | 2016-03-02T16:18:57.000+0000 |
Updated | 2018-08-06T17:34:44.000+0000 |
Description
Steps to Reproduce
-place breakpoints
-click debug view
-select 'debug' from dropdown menu next to green execute button
Actual Result
application executes all the way through without stopping at any breakpoints
Expected Result
appliction should stop at breakpoint and not continue until specified
Attachments
is this a known issue or am I an exception? Any quick work-arounds?
[~mkellogg91@gmail.com] we haven't received any issues about debugger. What you can help us do is give us a reproducible case, as well as the environment you have? and whether it's just simulator, or device etc.? as much info as you can then we can pinpoint the exact issue you are facing.
All of my versioning information is in the diagnostic log above. I will tell you that all of my development is done on emulators. IOS Simulator and I primarily use google nexus 10 - api 21, and google nexus 5 - api 21 for development. the steps I take to run debugging is listed above in the description, but it just runs past the breakpoints without stopping at all.
[~mkellogg91@gmail.com] Can you attach ios debugger log file. Here you can find.
Here is what I found in the log file you asked for:
Hello, I tested this issue in my environment. Debugging is working as expected both for iOS and android. *Testing Environment:*
*Steps to test:* - Create a project - Add breakpoint at a valid position - Run in debug mode Thanks.
I just created a new project and tried debugging and it didn't work. I'm expecting execution to suspend when it hits a breakpoint in debug mode, is this a correct expectation?
[~mkellogg91@gmail.com] Where did you put the breakpoint? And this maybe strange but, do you think you can try this in a different network? (or go offline and try)
I put breaklines on a function call and on lines inside the test function. Are there specific types of code that won't suspend execution even if it has a breakpoint? I will try offline and let you know what happens
Long story short, didn't suspend on execution. I unplugged ethernet and turned off wifi and tried running again. As you can see from the image I had placed breakpoints on the call of each 4 functions and inside the 4 functions as well, but no suspend. I've also included the output when I attempt to debug (only text after application starts). !http://i68.tinypic.com/9porvc.jpg! starting app: com.debugTester/.DebugtesterActivity [INFO] : Application pid: 2142 [INFO] : Forwarding host port 61572 to device for debugging -- Start application log ----------------------------------------------------- [INFO] : TiApplication: (main) [0,0] checkpoint, app created. [INFO] : TiApplication: (main) [17,17] Titanium 5.1.2 (2015/12/16 19:00 ca822b2) [INFO] : TiApplication: (main) [26,43] Titanium Javascript runtime: v8 [INFO] : TiRootActivity: (main) [0,0] checkpoint, on root activity create, savedInstanceState: null [WARN] : V8Object: (KrollRuntimeThread) [28,28] Runtime disposed, cannot set property 'userAgent' [INFO] : TiRootActivity: (main) [0,0] checkpoint, on root activity resume. activity = com.debugTester.DebugtesterActivity@21e535bc [INFO] : Project built successfully in 30s 805ms [ERROR] : Error: getaddrinfo ENOTFOUND platform.appcelerator.com at errnoException (dns.js:44:10) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:94:26) --------------------------------------------- at TLSSocket.Readable.on (_stream_readable.js:671:33) at tickOnSocket (_http_client.js:489:10) at _http_client.js:504:7 at process._tickDomainCallback (node.js:381:11) --------------------------------------------- at ClientRequest.onSocket (_http_client.js:499:11) at Agent.addRequest (_http_agent.js:166:9) at new ClientRequest (_http_client.js:154:16) at Object.exports.request (http.js:49:10) at Object.exports.request (https.js:136:15) at Request.start (/Users/michael.kellogg/.appcelerator/install/5.2.0/package/node_modules/request/request.js:747:30) at Request.end (/Users/michael.kellogg/.appcelerator/install/5.2.0/package/node_modules/request/request.js:1381:10) at end (/Users/michael.kellogg/.appcelerator/install/5.2.0/package/node_modules/request/request.js:575:14) at Immediate._onImmediate (/Users/michael.kellogg/.appcelerator/install/5.2.0/package/node_modules/request/request.js:589:7) [INFO] : OpenGLRenderer: Initialized EGL, version 1.4 [WARN] : EGL_emulation: eglSurfaceAttrib not implemented [WARN] : OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0xefd07ec0, error=EGL_SUCCESS [INFO] : testing1 [INFO] : testing2 [INFO] : testing3 [INFO] : testing4 [WARN] : EGL_emulation: eglSurfaceAttrib not implemented [WARN] : OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0xefd07ee0, error=EGL_SUCCESS [INFO] : APSAnalyticsService: Analytics Service Started
[~mkellogg91@gmail.com] with the network enabled, have you tried on device? [~jnaher]see if you can work with Michael and see if there's anything different from both your environments. both looks the same but somehow Jebun doesn't see any issues.
Resolving as
Done
as newer versions of Titanium use the native Safari- and Chrome-debugger protocol that does not have this issue anymore.Closed as completed. If this is in error, please reopen.