-
Notifications
You must be signed in to change notification settings - Fork 317
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
Unable to debug web apps using latest Flutter master / SDK DAPs #4413
Comments
@elliette FYI - this may affect today's testing. I did a release of Dart-Code today that re-enabled the SDK DAPs for users on latest An immediate workaround is to disable SDK DAPs with this VS Code setting: "dart.previewSdkDaps": false, Depending on the cause (and how quick a fix will arrive in the SDK) we may need to hot-fix Dart-Code to bump using the SDK DAPs further back (or at least do so in a pre-release version and users of Flutter (I'm looking into it and will post my findings shortly) |
This is the issue. Removing the code that tries to listen on this stream fixes the issue. I'm going to temporarily revert change to enable SDK DAPs in a pre-release version of the extension (so people testing have an option) but I'll hang fire on pushing out a stable release unless it's clear we can't fix this in Flutter |
Edit: moved to #4414 (comment) |
I originally thought this was only affecting the Dart Debug extension, but it's affecting Chrome too. I'm going to push a stable Dart-Code to delay enabling the SDK DAPs (Dart 3 pre-releases might mean more people on pre-releases) to resolve this, and have opened #4414 to track the proper fix. |
Fixed (by not enabling SDK DAPs by default for current Flutter pre-release) in v3.60.1 of the Dart extension. |
Thanks for the quick fix! Is there anything I should keep an eye out for? |
@elliette I don't think so. As long as you're on the latest Dart extension (3.60.1 stable, 3.61.20230302 pre-release) or previous versions from before today (3.58/3.59) and you haven't set Of course, if you do spot any issues that may be VS Code/extension related, let me know. It's unfortunate I didn't pick this up sooner - it would've been good if today's testing could've been done with the new DAPs (since the sooner we find any remaining issues, the better), but it is what it is. I'll re-enable the new DAPs with a new Flutter version number as soon as we have a fix and it gets into Flutter, so any future testing can hopefully be on that (I'm really keen to find any show-stoppers before the next stable branch so we can finally get stable users over to it 😄). |
When clicking the Dart Debug Extension button (edit: this happens on Chrome too, not specific to the debug extension), the connection is made but the app never loads.
Verbose logs contain this:
It's unclear which (if any) of these are causing the issue.
The text was updated successfully, but these errors were encountered: