rmawatson
Document whether the isolate continues to run after the app is killed.
From my experimentation I can't get the isolate to continue to run after the app is killed, please document if this is possible and if so how to achieve it.
Since my isolate code only relies on dart code it'd be great to avoid implementing the full background platform specific plugins as described here: https://medium.com/flutter/executing-dart-in-the-background-with-flutter-plugins-and-geofencing-2b3e40a1a124
A year later and he still hasn't said if this package works when app is killed. After spending so many hours getting the example to work, ultimately I found out that the isolate is killed when the app is killed. Pathetic. Everyone is coming to this package to handle tasks when app is killed. So this is basically false advertising. In your readme, if you precisely say that this package does not work when app is killed, I bet no one would even try to use your package and you wouldn't get even one download.
Will this isolate run after the app is closed? I am trying to find a similar functionality to that of Services in Android. Please confirm, thank you!
For anyone still looking for an answer, no the isolate is also killed when the app is killed. This is not a bug or problem with the package, it's just how isolates work, for now. I hope Flutter would have a better solution for background work in the future.
I believe that some (entitled?) people are asking (angrily?) for this package instead: https://pub.dev/packages/workmanager. FlutterIsolate does what it says on the tin.
Can you be a bit more specific? I didn’t watch the whole video but flicking through the time stamp you linked, it looked like she was registering a background service to perform tasks when the foreground app is killed.On 19 Feb 2023, at 7:33 PM, SmrutiSamratRansingh @.***> wrote: can any of u guys who say isolate is killed when app is killed have a look at this video https://www.youtube.com/watch?v=Hv0K5IaborA&t=1511s
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
