Skip to content

fix(debugger): listen for flutter.appStarted from the debug adapter - #564

Merged
sidlatau merged 1 commit into
mainfrom
fix/debugger-app-started-event
Oct 30, 2026
Merged

sidlatau merged 1 commit into
mainfrom
fix/debugger-app-started-event

Conversation

@sidlatau

Copy link
Copy Markdown
Collaborator
  • The DAP listener for app start now uses flutter.appStarted, the name Flutter's debug adapter forwards app.started under. Under the debugger, FlutterToolsAppStarted was never emitted, and the pre-start log buffer kept growing for the whole session and was scanned for device errors on exit.
  • Test drives a fake session through output → flutter.appStarted → terminated.

Fixes #563

The adapter forwards `flutter run --machine`'s `app.started` as `flutter.appStarted`, so
the `app.started` listener never ran: `FlutterToolsAppStarted` was not emitted under the
debugger and the pre-start log buffer kept every line of the session.

Fixes #563
@sidlatau
sidlatau merged commit 0ef43df into main Oct 30, 2026
7 checks passed
@sidlatau
sidlatau deleted the fix/debugger-app-started-event branch October 30, 2026 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] FlutterToolsAppStarted never fires when running with the debugger (DAP event name mismatch)

1 participant