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
[flutter_tools] allow filtering of adb logcat by "flutter" to be configured from CLI args #120711
ADB logcat logs are very verbose, so we filter it by lines that contain the pattern 'flutter'. We should make this configurable via a command-line flag, so that developers who want to debug the full logs can see this. This would also be leveraged by editor plugins, since--for example--Android Studio provides a UI for viewing full logcat logs in a natively launched application.
If the volume of traffic is high, there may be value in allowing it to be stopped/started while the app is running (via a message to the flutter run daemon, or over the a VM Service extension).
This could allow the user to start the log, perform some action in the app, then stop the log, rather than having to wade through large amounts of logging.
This debug line in particular really pollutes the log.
The prefix gives the log level: D/ is debug, W/ is warning, E/ is error. So in addition to the proposal of enabling or disabling the filter for logcat lines containing flutter, I suggest also allowing the user to set a minimum loglevel.
Reacted by Sam Deane, Azad, codenyte and Joe Muller
... however that is a potentially larger change. If the tool team is supportive of more aggressive Android filtering, I'd be happy to contribute here; removing triaged-tool to get an opinion before moving forward.
I'm all for reducing log spam but I don't have enough context to know whether or not it's safe to filter more aggressively. Is there a situation where we wouldn't want these logs filtered? Maybe @reidbaker will have a stronger opinion on this.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
DanTup commentedon Feb 15, 2023
If the volume of traffic is high, there may be value in allowing it to be stopped/started while the app is running (via a message to the
flutter rundaemon, or over the a VM Service extension).This could allow the user to start the log, perform some action in the app, then stop the log, rather than having to wade through large amounts of logging.
lukehutch commentedon Mar 14, 2023
Some logcat lines don't contain the string
flutter(unless that part of the line has already been suppressed):This debug line in particular really pollutes the log.
The prefix gives the log level:
D/is debug,W/is warning,E/is error. So in addition to the proposal of enabling or disabling the filter for logcat lines containingflutter, I suggest also allowing the user to set a minimum loglevel.LoveriusB commentedon Aug 10, 2023
matanlurey commentedon Oct 10, 2024
Fwiw, I looked into this briefly today.
... is not totally true - there are two branches:
flutterThe vast majority of so-called log-spam (e.g.
D/EGL_emulation) are in the current process ID, meaning its not filtered.I am very supportive to adding much more liberal
adb logcatfiltering, similar to what we did in the engine:https://github.com/flutter/engine/blob/main/testing/scenario_app/bin/utils/adb_logcat_filtering.dart
... however that is a potentially larger change. If the tool team is supportive of more aggressive Android filtering, I'd be happy to contribute here; removing
triaged-toolto get an opinion before moving forward.bkonyi commentedon Oct 15, 2024
I'm all for reducing log spam but I don't have enough context to know whether or not it's safe to filter more aggressively. Is there a situation where we wouldn't want these logs filtered? Maybe @reidbaker will have a stronger opinion on this.
3 remaining items
Resolve issue flutter#120711: Add --[no-]adb-log-filtering flag to by…
Resolve issue flutter#120711: Add --[no-]adb-log-filtering flag to by…
Support --[no-]adb-log-filtering CLI option (flutter#187252)
github-actions commentedon Sep 10, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.