-
-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugger does not stop at the app initial breakpoint #1437
Comments
Is there a workaround for this problem? Sometimes this works, most times it runs the app and doesn't launch node-inspector for Android. I have tried:
That has only managed to stop once in the inspector. Every other time it launches my app, then sits forever doing nothing. My login dialog (which should show) isn't... But when the debug worked that one time it showed up when I let the process keep running from node-inspector. |
Can you try to leave the emulator running and execute: |
It runs extremely slowly, but it seems to work. What happened was:
I can use this workaround, but hoping you all can figure this out soon. Thanks,
|
Here's an interesting note... I created a Chromium Remote Debug config for IntelliJ Idea to run the command Just an FYI |
I gave a try to the 1.6.0 release candidates and here is what I got out of
|
We changed the default behavior and debug will not longer stop on first code statement. I'm closing this. |
Tested with {N} CLI 1.6.0-524 and tns-android 1.6.0-2016.1.29.1.
tns debug android --emulator
starts successfully the node inspector, but it does not stop at the initial breakpoint set in prepareExtend.js. The same command works correctly if--emulator
is not specified.The text was updated successfully, but these errors were encountered: