Jenn Magder

> * The escape sequence at the start of the line is mangled That's exactly how it's coming from lldb. How does it look in Xcode?

Probably need to de-mangle it and pass along the color encoding? I haven't investigated this, that's why it's not fixed. 🙂 https://www.lihaoyi.com/post/BuildyourownCommandLinewithANSIescapecodes.html#256-colors https://github.com/flutter/flutter/blob/33b183e6c9874a8936f05defa12129bdc62c8099/packages/flutter_tools/lib/src/base/terminal.dart#L166-L172

ios-deploy could take a power-assertion while attached.

anaconda swaps out lots of build systems Flutter and Xcode are relying on, so I'm not surprised `conda deactivate` would fix your issues. See https://github.com/flutter/flutter/issues/43713 Can we get: 1. https://pastebin.com/XAvC6UmP...

`anaconda` and Flutter do not play well together--anaconda is swapping out tools from underneath Flutter.

Thanks for linking the two @moribellamy, that issue should have been duplicated to this one. Closing this as fixed in master and stable then, let me know if there's anything...

Is this different from https://github.com/flutter/flutter/issues/49101 or https://github.com/flutter/flutter/issues/45714? On the iOS side this would be easy to do if `.flutter-plugins-dependencies` indicated which were dev-only.

https://github.com/flutter/flutter/blob/bb29c88ae7acd49eda7e4a63b19a41c1de7a8247/packages/flutter_tools/lib/src/plugins.dart#L1172-L1183 > That probably requires generating a new plugin registrant based on which target the user is running Why would the native-side app ever need to register dev_dependencies?

Then shouldn't the test target be handling the registration?

With the addition of integration_test in every pubspec this opts every app into a dependency on CocoaPods. `pod install` will always run immediately after a `flutter create` with no additional...