-
-
Notifications
You must be signed in to change notification settings - Fork 245
App Crashes When Killed While Foreground Service is Active #1082
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
Comments
Simmilar: I do not have foreground service. https://github.com/PixsaOJ/ns-vue-router-unmount-error
I get exact same error. |
I think its the same issue, because its not producible if i fully reopen app from app drawer and Error log is the same |
This issue has been discussed on Discord as well, but unfortunately no solutions have been found yet. You can check out the conversation in the thread below: https://discord.com/channels/603595811204366337/606457523574407178/1260165032566722610 |
I just found solution. Might not be for everyone, or the final solution. I applied this patch:
to here:
node_modules
I do not know if it works for you |
I am experiencing an issue with my app when it is killed while foreground services are running.
In my app, the entry frame (Antre) navigates to a page (Home) and that page starts the service. When app is killed while the service is on, it skips Antre and opens Home right away. The reopened app does not work as expected. Afterwards, when the app is killed again while service is still running, it crashes with the following error. It seems the navigation stack is not cleared properly
The issue gets solved when I comment out the following if-check in node_modules/nativescript-vue/dist/plugins/navigation.js
You can find the steps and the repo to reproduce the bug below.
Repository to reproduce
Steps to reproduce the bug
Additional context: My app starts a foreground service to get the user's location, and I use Firebase Analytics to handle notifications. This problem occurs on Android 13.
The text was updated successfully, but these errors were encountered: