Hennie Brink

This happens because we do flutter engine reference counting to keep the location service alive when location is used in conjunction with another package like flutter_background so that location service...

I doubt that is what's causing this. It would be the reference counting of the active flutter engines doing this.One possible way to solve this would be to keep a...

I think there is a misunderstanding here. If you want the location services to stop when the application is killed then do not configure a foreground notification. The intention of...

You can still use the flutter background plugin to accomplished this. It will be a lot more reliable than just using the foreground notification built in with this package.On 22...

We can't do this globally for all apps that use this library. If you don't need background location then don't pass in the foreground notification or override the geolocatoe service...

Unsubscribing from the position stream so that you don't listen to it anymore should do the trick.On 19 Jul 2024, at 10:41, Hussen Ibrahim ***@***.***> wrote: how can forcefully stop...

Also running into this now. Seems to be a regression that was introduced at some point. I originally made the PR to do the reference counting and will have a...

Not yet noOn 10 Feb 2024, at 17:21, Ferry ***@***.***> wrote: Also running into this now. Seems to be a regression that was introduced at some point. I originally made...

That is definitely possible. In fact that is what I am doing in my app. Starting the foreground service means in my mind that the intent of the developer is...

If that's the case I'll take a look. I am using Geolocator in the same manner. On 21 Mar 2024, at 13:19, Fesp ***@***.***> wrote: @Wackymax In my situation it...