This repository has been archived by the owner on Nov 8, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 76
Geolocation background service not relased. #155
Comments
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. |
VladimirAmiorkov
added a commit
that referenced
this issue
Sep 10, 2018
VladimirAmiorkov
added a commit
that referenced
this issue
Sep 12, 2018
Hi @LorenDorez , |
@LorenDorez We have released a possible fix in nativescript-geolocation@4.3.1. Give it a try a let us know the outcome. |
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.
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?
The text was updated successfully, but these errors were encountered: