Add initial debugging instructions #168
Conversation
Provides basic instructions for debugging the Flutter side of a desktop application, since the normal approaches for Flutter debugging require some modifications on desktop. Related to issue google#14 and issue google#164, although doesn't fully address either.
| ``` | ||
| { | ||
| "name": "Flutter Desktop Attach", | ||
| "request": "attach", |
There was a problem hiding this comment.
This didn't attach for me until I added "program" : "example/flutter_app/lib/main.dart". Is this the case for you as well?
There was a problem hiding this comment.
Sounds like you opened the repo root in VS Code, rather than opening just the Flutter application as the instructions mention to do. program shouldn't be necessary in general.
There was a problem hiding this comment.
Yeah, I was still in root since I was already working there. Thanks!
Debugging.md
Outdated
| You will likely want to hard-code your observatory port, otherwise you will | ||
| need to change `launch.json` every time you relaunch the app. | ||
|
|
||
| In addition to the Flutter debug commands, source-level debugging with pausee, |
|
|
||
| ### Command Line | ||
|
|
||
| The `flutter attach` command can connect to a desktop Flutter application |
There was a problem hiding this comment.
Not sure if this is obvious, but might be worth clarifying that this command should be called from a directory that contains 'lib/main.dart'. I was getting an error when trying from another directory.
There was a problem hiding this comment.
I was assuming people using the command-line instructions would be familiar with needing to run flutter commands from the Flutter application directory, but it can't hurt to add. Done.
Provides basic instructions for debugging the Flutter side of a desktop
application, since the normal approaches for Flutter debugging require
some modifications on desktop.
Related to issue #14 and issue #164, although doesn't fully address
either.