Hennie Brink

Looking at the commit history the default behaviour of the intervalDuration was changed in [8.0.4](https://github.com/Baseflow/flutter-geolocator/pull/943) but that change was not documented in the change log.

@florissmit1 @mvanbeusekom we should maybe just update the change log indicating the behaviour change?

Also fixed in https://github.com/Baseflow/flutter-geolocator/pull/1057

@gusgonque can you try again with the latest release?

Was a cocoa pod configuration issue on my side

@mvanbeusekom I will have a look at it

Having a look at the code it seems like even though the service is starting in the foreground it is still dependent on the activity and the flutter engine associated...

Ok that is a separate issue that I can help fix > On 02 Mar 2022, at 16:54, Bujdy ***@***.***> wrote: > >  > @Wackymax I understand its a...

I am not going to have time to fix it this week, but the fix would be to stop the service when the activity is detached from the engine and...

PR to unbind the service is up