-
Notifications
You must be signed in to change notification settings - Fork 122
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
Crash in production #112
Comments
|
Hi @X-SLAYER , Do you have any plan on this to resolve. Thanks |
Happened on debug as well, I have google pixel 7 |
Android may decide to kill the overlay service for various reasons (e.g. low ram), and since START_STICKY is used it may later decide to restart the service. When this happens OverlayService.java tries to access variables which were created outside of the service and are no longer set, for example You have two options to avoid these crashes:
Apart from explaining why this happens the only other help I can really offer is a suggestion of how to reproduce the error if you want to keep START_STICKY and try to fix it yourself:
|
@X-SLAYER Do you plan to release a fix to this issue as it's still reproduceable in the latest version? |
Done! the package has been updated with the instructions for android 14 compatibility |
@X-SLAYER Thanks for your quick reply but the issue is not related to android 14 only as i can reproduce it on more than android version like android 13 and android 12 (these are the devices that i have and it may be reproduced on more).
|
Hello @X-SLAYER ,
Thank you soo much for having such an awesome plugin for flutter.
I want to bring one issue to your attention that is happening in the production.
Here's the stack-trace from firebase-crashlytics.
please let me know if you need further information from my side.
thanks
The text was updated successfully, but these errors were encountered: