Martin Kustermann

> Ok, we should be good-to-go here, we have consensus to land single-approved workloads under /experimental. @camillobruni Should we wait until https://github.com/WebKit/Speedometer/pull/519 landed?

So from my understanding this isn't related to `package:native_assets_cli` at all. The situation seems to be as follows and only problematic due to `package:logging` dependencies: * `flutter update-packages` will update...

I've landed https://github.com/flutter/flutter/commit/31c1292be3fa0b4bac3ed05f035a816ba028f5e1 which should make the native asset test more robust and not cause this version constraint conflict despite still using pinned deps for it's test. @christopherfujino @matanlurey how...

I've now both, landed https://github.com/flutter/flutter/commit/31c1292be3fa0b4bac3ed05f035a816ba028f5e1 which should avoid this issue in the future for this native asset test as well as rolled the native asset packages. As I don't know...

Just to clarify: The flutter engine supports multiple UI isolates. It intentionally runs all of them on the same thread. It may be that the flutter embedding API you use...