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
Our console output when running xCode builds is very noisy and hard to read. We heard very good things about https://github.com/supermarin/xcpretty from another team that runs xCode builds, so would be good to give that a try for Flutter.
Since building the dart snapshot via script is one of the main components of the xcode build phases, having its output not show up is pretty inconvenient.
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
[-]improve xcode output with cxpretty[/-][+]improve xcode output with xcpretty[/+]xster commentedon Feb 5, 2018
xcpretty doesn't have a brew formula which is unfortunate. We'd have to make it very optional since the user have to wrangle with ruby gems
mit-mit commentedon Feb 6, 2018
Is there no way of bundling xcpretty into our SDK?
xster commentedon Feb 9, 2018
There's actually something rather inconvenient with xcpretty
xcpretty/xcpretty#163
Since building the dart snapshot via script is one of the main components of the xcode build phases, having its output not show up is pretty inconvenient.
When it fails, xcpretty just shows:
xcodebuild's stderr still shows
which is still semi-useful. But only the original xcodebuild's stdout contains the useful debug information:
[-]improve xcode output with xcpretty[/-][+]Clean up xcodebuild's messy output[/+]xster commentedon Feb 9, 2018
For reference, I have a PR to use xcpretty (https://github.com/flutter/flutter/compare/master...xster:xcpretty?expand=1) but I think we shouldn't use it if it doesn't show any snapshotting output.
Going to clean up the existing xcodebuild's stdout instead for now.
xster commentedon Feb 9, 2018
With #14586, a failed build's output will be:
I think it's good enough.
github-actions commentedon Sep 3, 2021
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.