Skip to content
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.

Geolocation background service not relased. #155

Closed
LorenDorez opened this issue Aug 26, 2018 · 3 comments
Closed

Geolocation background service not relased. #155

LorenDorez opened this issue Aug 26, 2018 · 3 comments
Assignees

Comments

@LorenDorez
Copy link

I have an app running Geolocation in a background service just fine. However, if there is an app error and the user force-closes the app this doesnt terminate the watchlocation listeners. Then if the user starts another watchlocation there are essentially now 2 running but only able to clear the new one as the old one is abandon and lost in space. How can I handle terminate or retarting the watchlocations across app closes?

@VladimirAmiorkov
Copy link
Contributor

Hi @LorenDorez ,

Thank you for reporting this to us.

We see what you mean and we are going to implement an internal cleaning of all "watcher" listeners when the application experiences an critical error on both Android and iOS. Look forward to the next version of the plugin coming soon.

@zbranzov
Copy link
Contributor

Hi @LorenDorez ,
Is there a way to check the leaked processes, because I cannot reproduce your case?
I install the app on Nexus 6 Android 7.1.1, start the background service and crash the app. Then, when I check the running services (Developers Options > Running services) there isn't any started from my app.

@zbranzov zbranzov self-assigned this Oct 2, 2018
@zbranzov
Copy link
Contributor

zbranzov commented Oct 3, 2018

@LorenDorez We have released a possible fix in nativescript-geolocation@4.3.1. Give it a try a let us know the outcome.

@zbranzov zbranzov closed this as completed Oct 3, 2018
@ghost ghost removed the ready for test label Oct 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants