Repository navigation
Flutter should not print the E/SurfaceSyncer messages about Failed to find sync for id= #123255
Description
There is a little more context on this in b/268445629, cl/494699962 (sorry, Google only).
From a member of the Android team at Google:
Thanks for the bug report. This issue is fixed in Android U. Besides the spammy logs, this shouldn't be causing any issues.
A Google-internal Android framework also ignores this message. The message can become very spammy and concerning to users (see e.g. https://stackoverflow.com/questions/73432326/failed-to-find-sync-for-id-0-in-flutter), especially if it is covering up otehr problems.
/cc @reidbaker fyi, @christopherfujino - I'm pretty sure we have things in the android logging logic to ignore other messages already.
Reacted by Greg Price and Uvais-Mohammad
Activity
[-]Flutter should ignore the `E/SurfaceSyncer` messages about `Failed to find sync for id=`[/-][+]Flutter should not print the `E/SurfaceSyncer` messages about `Failed to find sync for id=`[/+]gnprice commentedon Mar 22, 2023
Sounds great. There's another log message that tends to appear at the same time (as seen in #116669, for example):
That one was also reported in #119128 and #119935, as well as several StackOverflow questions. I'd guess (or hope) that it's equally harmless and unactionable.
Do you happen to know anything about that one from the same internal threads? (If not, then perhaps it should get a separate issue thread.)
dnfield commentedon Mar 23, 2023
I think that message is also safe to ignore. I tried a few searches and didn't find it specifically, except incidentally included in other bug reports where it basically was ignored.
We could filter on that one, although it comes up less frequently. I got fed up with this one because in a recent bug I on a particular device i was working on it was coming up very frequently and making it impossible to read any other logs.
github-actions commentedon Apr 6, 2023
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.