-
Notifications
You must be signed in to change notification settings - Fork 316
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 stuck on waiting for connection from debug service on chrome when trying to run on web using Flutter 2.x #4370
Comments
@felipefranca824 from the error in your screenshot, it looks like there is a problem with the code (trying to use Does fixing that issue resolved the problem? If not, can you produce a small sample project that triggers this issue that you can share? Thanks! |
@DanTup but if i run by command line "fllutter run -d chome" it works |
@felipefranca824 can you reproduce this reliably? Did you make any changes to the sample project, or run it as is (and how did you start it?). Could you try capturing debugging logs while reproducing it (using the sample project)?
Thanks! |
@DanTup I sent the log file to your email |
@felipefranca824 thanks! I found the issue in your log:
This was a bug in earlier versions of Flutter (dart-lang/webdev#1627). It's since been fixed but you'll need to upgrade Flutter to a more recent version to get the fix (the current version is 3.7). The reason it works from the command line is that this doesn't set up the debugger, which avoids the code that is failing. Please let me know if you still have the issue after upgrading! |
After updating the problem was solved. to continue using in older versions of flutter I used version 3.56.0 of the dartcode extension. thanks |
Oh, I see what's happened here. The new version of the extension is using a new version of the API, but there's a mismatch between the VM Service version that supports this in DWDS (web) versus the standard VM. This is unfortunate, although since the latest stable versions of everything are working (and using the previous extension works around the issue) I think it's probably not worth trying to find a way to handle this for now. If it turns out the issue is widespread, we can re-visit this. Thanks! |
I'm getting this issue revisiting a flutter web project there hasn't been touched for 7 months - so very likely one of the latest dart extension upgrades is the culprit - its very annoying and i do not really wanna do a 2.x 3.x upgrade as we're close to go-live for a large client |
@psimondk the quickest fix would be rolling back the Dart extension to v3.56: I'll have a look to see whether there's a version we can gate on that avoids this issue for both web/non-web. |
I've updated the version for when the extension start using the new API to something I believe works for both cases. If you switch to the Pre-release channel for the extension, you'll get this fix now without needing to use an older version of the extension: You can switch back to the stable versions of the extension after the next release (or, stick with this - it should generally be stable anyway, as it's usually only published to make fixes like this available to people a little sooner). |
And I can confirm that it works like a charm - thanks a lot for stepping up
to help on this - we had a very good demo for a German Client last friday
and now we can debug our accompanying dashboard too!
[image: image.png]
Best Regards, Palle S.
…On Mon, Feb 13, 2023 at 2:22 PM Danny Tuppeny ***@***.***> wrote:
I've updated the version for when the extension start using the new API to
something I believe works for both cases. If you switch to the Pre-release
channel for the extension, you'll get this fix now without needing to use
an older version of the extension:
[image: Screenshot 2023-02-13 at 12 19 54]
<https://user-images.githubusercontent.com/1078012/218456057-b695fd12-3db0-471e-acd8-4c267993680b.png>
You can switch back to the stable versions of the extension after the next
release (or, stick with this - it should generally be stable anyway, as
it's usually only published to make fixes like this available to people a
little sooner).
—
Reply to this email directly, view it on GitHub
<#4370 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP6EPLFFGWTDHPABPNNFRDWXIROVANCNFSM6AAAAAAUMMWKPI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hello, I encountered the issue too on a Flutter 2.10.5 project. Thanks |
Hello, If it can help someone... I had the same issue on a Flutter 2.10 project using Android Studio and Flutter plugin (version 73). Here are the steps :
And it works :-) |
If you are using VPN, please disconnect/logout. And try again. It will work in my experience. |
Describe the bug
Debugger stuck on waiting for connection from debug service on chrome when trying to run on web
To Reproduce
Steps to reproduce the behavior:
Expected behavior
project was supposed to run normally
Screenshots
Please complete the following information:
The text was updated successfully, but these errors were encountered: