Jenn Magder
Jenn Magder
> Taking that into account, I guess removing it should not be the best way to work this out, rather than always committing the changes made on the Podfile.lock so...
@stuartmorgan does the current behavior align with the exception handling patterns in the package repo?
> I think we should audit the existing x64 targets one by one Check out [go/flutter-mac-test-architectures](http://go/flutter-mac-test-architectures)
@dvird Please don't @ individual contributors. I don't generally work on these kind of bugs.
Maybe this is framework?
\cc @bparrishMines
@godofredoc Let me know when you have the recipe and modules updated with `FLUTTER_LOGS_DIR`, I have a PR to test it out at https://github.com/flutter/flutter/pull/74378
@godofredoc This will be helpful in the engine as well as the framework. 😄
@godofredoc this is done in the engine as well, right? Can we close?
@godofredoc is there any way we can prioritize getting this done in the engine repo? It's really hard to debug failures like https://github.com/flutter/engine/pull/26786#issuecomment-862724209 without the uploaded test results.