devtools setting breakpoints doesn't work when devtools is launched from IntelliJ

I'm not able to consistently set breakpoints in the debugger page.

May 30 '19 20:05 devoncarew

This seems to happen when you've launched devtools from IntelliJ.

May 30 '19 20:05 devoncarew

I'm having trouble reproing this now.

Jun 08 '19 21:06 devoncarew

This may happen after a hot restart is performed; the older breakpoints may not be removed, and may still point to the previous scripts (and, new breakpoints for the new scripts are not set).

Jun 08 '19 21:06 devoncarew

Most of the issues do seem to be related to breakpoints (and other debugger features) not working as well after the app has been restarted. I think after a restart we'll need to re-load the list of scripts (and update this in the UI).

I don't believe we get an event when a script is re-loaded (via hot reload). We get a kPausePostRequest event which we can use to know we have to reload some data.

It could also be useful for the VM to fire an event after a script is reloaded (not for the ~800 initial scripts, but for deltas after an isolate has started). This could be generally useful for tools. cc @bkonyi

Jun 10 '19 15:06 devoncarew

Set the milestone for this one aggressively to 0.1.2. The issue is indeed hot restart/reload related. We need to re-initialize breakpoints after a restart/reload and there are some tricky edge cases we need to work through when multiple IDEs are connected.

Jun 17 '19 23:06 jacob314

This was fixed with https://github.com/flutter/devtools/issues/7231

Nov 19 '24 22:11 elliette