-
Notifications
You must be signed in to change notification settings - Fork 311
Version 0.0.30 components can't be debug bug #110
Comments
@six006 please do not delete the issue template. Update your issue with the issue template and the info for it. |
Hello, thanks for opening an issue with us! Would you mind giving a little more info on what exactly is happening here? I was able to put in breakpoints fine in my testing apps. |
Thanks! So im getting closer to figuring out what is going on here, breakpoints are working, but the line numbers seem to be "wonky". If i put a breakpoint on two different methods in my test project, click a button to call that method the breakpoint, the debugger stops on a breakpoint, but seems to be stopping on the wrong one. |
I recently noticed that ts sourcemaps were behaving weirdly in Chrome. It's a long shot, but try it with |
@Kobzol Disable cache is always on in my environment. So, isn't that. |
I guess this is the right thread concerning the issue with sourcemaps causing typescript breakpoints working weirdly, and step-by-step sometimes jumping to the js bundle. I am experiencing the same, and this is the setup I am using:
Various folks have posted this issue in other threads (#32 and ionic-team/ionic-framework#8292). Again, with ionic framework beta breakpoints were working flawlessly using the same setup. |
I have tested pull request 126 and now I can debug properly. Please merge it for the next version Edit: Edit2: |
To be able to debug on device we need that
Thanks At now I have to do to much tricks to get it working: Close android app and restart the app Edit: To enable the watch process using "ionic run ...." I have modified my package.json |
With the latest master i can happily report that this has been fixed! Breakpoint line numbers now line up exactly like they should. Thanks everyone! |
Are you sure?
Edit: Edit2: |
Finally I can debug with latest version!!! |
The page can't be debug,

The text was updated successfully, but these errors were encountered: