-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Constant crashing used with foreground service #25
Comments
FWIW, I am aware of #12 and did follow the advice to move all the accessibility requests to the main activity. However, by definition my foreground service exists only to watch the accessibility event stream - opening our app if certain conditions are met. Hence, the only call I make in the foreground service is invoking |
Also, Flutter Doctor output here, for versions etc:
|
I'm also facing the same issue when i'm calling stream foreground service any fix....? |
@X-SLAYER any fix...? |
i will try to investigate on this problem |
|
@X-SLAYER any solution |
I found a workaround that worked for me (tested with
This will resolve the error and prevent the app from crashing when exited. See extended example:
|
Start fine, but there's some sort of lifecycle issues which inevitably cause it to loop-crash.
I've tried a few different approaches to handle the lifecycles, initialisation, and isolate management, but I have been unable to find an incantation that prevents these errors:
These errors have been preventing us from launching our app for many months now and I simply cannot find a way round them. Any help would be gratefully appreciated! Absolutely mission critical.
FYI: our foreground service runner is https://pub.dev/packages/flutter_foreground_task.
Error 1
Error 2
Error 3
Error 3
The text was updated successfully, but these errors were encountered: