You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] FlutterToolsAppStarted never fires when running with the debugger (DAP event name mismatch) #563
When the app runs through the debugger runner (debugger.enabled = true), the FlutterToolsAppStarted User event is never emitted. Autocmds listening for it never run, and the statusline decorations in decorations.lua are not refreshed on app start.
debugger_runner.lua listens for a DAP event named app.started (lines 187 and 238):
Flutter's debug adapter never sends a DAP event with that name. app.started is the event flutter run --machine emits. The adapter receives it internally (handleJsonEvent in flutter_adapter.dart) and forwards it to the DAP client as flutter.appStarted:
Suggested fix: change event_app.started to event_flutter.appStarted in both places in lua/flutter-tools/runners/debugger_runner.lua. With that change applied, the repro above prints FlutterToolsAppStarted fired right after the DAP event.
I can open a PR.
Thanks for the detailed report and the repro, the analysis was spot on. Since the fix is a two-line rename, I went ahead and opened #564 with your suggested change and a test for it.
The same listener also sets the "app started" flag that clears the pre-start log buffer, so besides the missing FlutterToolsAppStarted event, debugger sessions were keeping their whole output in that buffer until exit. The fix covers that too.
Activity
sidlatau commentedon Oct 30, 2026
Thanks for the detailed report and the repro, the analysis was spot on. Since the fix is a two-line rename, I went ahead and opened #564 with your suggested change and a test for it.
The same listener also sets the "app started" flag that clears the pre-start log buffer, so besides the missing
FlutterToolsAppStartedevent, debugger sessions were keeping their whole output in that buffer until exit. The fix covers that too.fix(debugger): listen for flutter.appStarted from the debug adapter (n…