stuartmorgan-g

Tests are green! 🎉

This looks like a crash: ``` [==========] Running 15 tests from 5 test suites. [----------] Global test environment set-up. [----------] 1 test from MultipleArity [ RUN ] MultipleArity.HostSimple [packages/pigeon completed...

I though maybe the unit test might need GTK initialization to work (that's been true of other Linux unit tests in the past) so I added an `xvfb` wrapper. It's...

> * The test runner not clearly marking when things fail (e.g. return code or signal that occurred) We should probably have the Pigeon test runner log any non-zero return...

There's currently no way to pass a verbose build flag through the Pigeon tooling (although we could definitely add one), but the build is just a `flutter build linux` in...

@gspencergoog Should the test be brought back out of bringup now? It looks like it's been green since you landed your PR.

Re-opening since the PR didn't fix all codepaths. And in particular, the original report's stack is in `handleChooseMultiImageResult`, which is the one that's not fixed.

> I suggest you make a new **flutter_blue_plus_for_windows** package on pub.dev. > > Then in **flutter_blue_plus_for_windows** you can create a platform channel using the existing `flutter_blue_plus/methods` name. > > [...]...

> * The desktop package maintainer could and should use version constraints that block using newer versions that are likely to be incompatible probably allowing patch but not minor version...

> these problems apply to any package and it's maintainer I have never seen another instance of a package maintainer explicitly encouraging people to publish packages that use internal implementation...