Bryan Oltman

I believe we only forward verbose output when the invoked command fails (https://github.com/shorebirdtech/shorebird/blob/main/packages/shorebird_cli/lib/src/process.dart#L213-L214). I forget the exact conversation that led to this decision, but I believe we were trying to...

But either way, invoking the `flutter build` command manually should print what you want to see

It's possible the right solution would be to add an extra level (or levels) of verbosity to the CLI that would log stdout/stderr regardless of whether the invoked command failed.

Context: Since this was filed, we've updated the CLI to pass the `--verbose` flag to flutter when it's passed to the CLI. We (I think I was the one who...

From https://github.com/shorebirdtech/shorebird/issues/1789: > The original design goal of adding this to shorebird preview was to reset the app back to a "fresh from store" state (no patches installed). But it...

I think this has been resolved? Closing, as we haven't had any reports of this since last activity on this issue.

Note that this also happens in Flutter 3.13.9, although they handle it more nicely. If I try to `flutter run` in this case, I see: ``` Could not build the...

I remember us discussing this as a potential need when we first supported hybrid apps, but I don't believe I've heard anyone asking for this.

Re: the discord comment about building the patch twice, that's actually just a quirk of mason_logger. Writing a non-progress log message while a `progress` is spinning will result in that...

This is a good idea. I filed https://github.com/felangel/mason/issues/1202 with the CLI library we use, which is where the first bit of work for this would take place.