Danny Tuppeny

I actually think we should support fixing all errors (that `dart fix` would fix). Currently we prompt "Your project has errors that can be corrected with `dart fix`" and make...

Understood. I think both should be possible, and there's probably a difference in which fixes are available in each. I think there are fixes that are appropriate to run across...

Are you able to post a screenshot of the entire VS Code window both when you _do_ see your device, and when you do not see your device? Can you...

The devices shown in the first screenshot are emulators that have not been started up yet. Can you confirm what happens when you select one? You should see an emulator...

Could you try enabling the Flutter device daemon log by adding the following to your VS Code settings? ```js "dart.flutterDaemonLogFile": "C:\\Logs\\flutter_daemon.txt", ``` Replace this with an appropriate path for your...

@Psyk0Path thanks - it looks like ADB reports that the emulator doesn't exist when Flutter tries to query some parameters: ``` // Request to start emulator [6:40:47 PM] [FlutterDaemon] [Info]...

Oh, I think this is working as expected. You can only use _active_ devices when starting to debug. If your emulator is closed, it is not considered an _active_ device....

This is unfortunately a known limitation of how we can run tests with `dart test`. There's no ability to "run tests in group x" we can only "run tests whose...

I need to test this, but I think this may be solved by running tests by line numbers.

I tested this and confirmed that this now works: Checking the launch config, this is indeed because we use the line number instead of the name to start the test:...