Nick Fisher

Thanks @indrajit-roy - I just verified that the spawned isolate will continue to run after the FlutterActivity is destroyed (and the app is in AppLifecycleState.paused). Assuming you were given the...

Looks like the main Dart executor is killed when the activity is destroyed (and possibly the native plugin instance, I'd need to check), but if we make the native isolate...

@ened can you provide a bit more detail about your use case? The current assumption is that registerWithRegistrar is called once (and only once) in the app lifecycle, but it...

Thanks @ened - I think I understand your issue now: 1) you're working with isolate(s) spawned by flutter_isolate, and isolate(s) spawned by separate Flutter Engine(s)/plugin(s), 2) plugins created in the...

Thanks @ened

Probably the same recurring issue with incompatible plugins. This is unlikely to be fixed in the near term, but can you post a link to the torchlight Android/iOS plugin code...

I have an open issue to update the whole `flutter_isolate` plugin for compatibility with `FlutterEngineGroup` (see https://github.com/rmawatson/flutter_isolate/issues/73), but at the moment I don't this will work as-is. I did some...

@cdoco unfortunately isolates are not attached to an Activity (see https://github.com/rmawatson/flutter_isolate/issues/71#issuecomment-827329925 for further details) and I'm not sure if there's a catch-all solution for doing so (arbitrarily spawning a new...

Unfortunately due to the way that `flutter_isolate` creates new isolates (by creating a new FlutterEngine), many plugins will have incompatibilities that have to be addressed on the plugin side (or...

Can you provide a sample project to reproduce this issue? Without any further information it looks like a Flutter/Dart isolate issue.