Dart-Code: "Select Device" doesn't work if the daemon has terminated, but provides no feedback

Describe the bug After a bit of usage, tapping the device selector in the bottom right results in no action. The “Flutter: Select device” command also does nothing. Only restarting VS Code fixes the issue, temporarily.

To Reproduce Unclear for now

Please complete the following information:

Operating System and version: macOS Ventura
VS Code version: 1.77.3
Dart extension version: 3.62
Dart/Flutter SDK version: 3.10.0-10.0.pre.17

Logs

Wed Apr 26 2023 [10:46:07 GMT+0200 (Central European Summer Time)] Log file started
[10:46:10 AM] [General] [Info] Returning cached promise for getSupportedPlatforms()
Wed Apr 26 2023 [10:46:12 GMT+0200 (Central European Summer Time)] Log file ended

About this issue

Original URL
State: closed
Created a year ago
Comments: 18 (11 by maintainers)

Most upvoted comments

Can you try enabling the daemon log in your VS Code user settings and getting a copy next time you see this?

// relative paths will be relative to the open workspace, but absolute paths work (though multiple open VS Code instances may overwrite each others)
"dart.flutterDaemonLogFile": "logs/flutter_daemon.txt",

I wonder if maybe the daemon is crashing? This came up in #4475 but I don’t know what would cause it. If it’s common for the daemon to crash we should probably restart is silently and file a flutter/flutter bug.

If this was happening, you should see a toast notification saying it had terminated though.

DanTup on Apr 26, 2023