-
Notifications
You must be signed in to change notification settings - Fork 323
Web device is not being detected when running VSCode from icon launcher #4778
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
Comments
Can you run the Flutter: Run Flutter Doctor command from the VS Code command palette (not from the built-in terminal) and post the output? My feeling is that the |
This output (running Flutter: Run Flutter Doctor) is when VSCode is run from terminal:
This output (running Flutter: Run Flutter Doctor) is when VSCode is run from icon launcher:
|
According previous output, Flutter is no detecting binaries paths when launching from icon launcher. this didn't happen before |
This is likely because of setting Can you try enabling the Flutter Daemon log (https://dartcode.org/docs/logging/#flutter-daemon) using the |
|
Looks like we're never getting any devices from the daemon. Can you try running:
in a terminal, and then paste the following in and press
Then wait for 30 seconds, hit Crtl+C to terminate the process, and share the output here. My guess is that Flutter isn't discovering the web device but I'm not sure why (since |
|
Oh, that didn't help much - because the Chrome device is showing up when you run from the terminal. Could you try enabling the log file again, but also passing "-v" to Flutter processes by using the following in your VS Code settings:
You can set the log path to anything. Then reload VS Code, trigger the issue, then grab a copy of the log file. Remove the settings once you're done (because the last setting will cause Flutter to generate verbose output for all processes). Thanks! |
I added those settings then restarted VSC and tried run my app, this is the output:
|
Thanks! It looks like we're spawning the daemon without the
I'll see if I can track down why that's being lost. |
Apparently I broke this when implementing 41fc23b. Will push an update to the pre-release channel including the fix later today. |
I've published a pre-release version with this fix so if you need it before the next stable update you can get it by switching here in VS Code: It might take ~20min for the update to show up - it'll be version v3.75.20231009 and you'll need to click the Reload button after installing. The pre-release should be pretty stable so there shouldn't be any urgent need to switch back. Please let me know if you still have any problems with that version. |
Web device is recognized now, I'll be testing this pre-release version along day I hope my PC doesn't go off , worse it doesn't even recognize me ;) |
Great, thanks for confirming! There's very little difference between stable/pre-release right now and there are quite a lot of users on pre-release, so I think you should be safe :-) (but if you do hit any issues, please do let me know!) |
Describe the bug
Web device is not being detected when running VSCode from icon launcher but if it's run from terminal.
To Reproduce
Steps to reproduce the behavior:
Flutter detects Web device in both cases:
This problem has emerged since the most recent VSCode and Flutter update .
More info
I'm using the following setting (see this post)
I have similar environment variable in my
.zshrc
file.Expected behavior
Either by icon launcher or from terminal the Web device should be available to select:
Screenshots
If applicable, add screenshots to help explain your problem.
Please complete the following information:
You can run the Dart: Collect Diagnostic Information command from the VS Code command palette (
F1
) to easily capture this information or provide it manually.The text was updated successfully, but these errors were encountered: