IOS clients stop reporting location in background

[pbelbin]

I have a bunch of Apple Traccar Client users that are reporting that location updates are not running continuously when in the background.

They're using the latest version of the app via the app store.

App settings are set to enable all of the requested permissions that should allow the app to run continuously.

It's unclear whether it's just IOS 26 users or whether it's affecting all IOS users.

This is very third-hand information, but, it does seem there's a problem.

Android, in contrast, seems to be working very reliably.

[tananaev]

Really need to look at the logs to see what happens. It is normal for app to stop reporting if there's no movement. And it take ~200m to start reporting again.

[pbelbin]

Understood. But, this is from multiple users, and from what I understand, they resort to restarting the app. This is people that are mobile, and the app stops reporting their location. They discover their location is no longer being reported, and then they go and restart the app.

[pbelbin]

200 meters of movement is a lot of distance for some situations. But, I expect the people in this case are moving more than that, if I understand correctly. I'm curious why it's 200 meters of movement that's required to restart reporting location. Any insight you can share on that? Seems odd given the app allows a distance to be supplied that would often be less than 200m.

[tananaev]

I recommend reading this documentation:

https://github.com/transistorsoft/flutter_background_geolocation/wiki/Philosophy-of-Operation

It will help you understand where 200m is coming from and how the system works in general.

[pbelbin]

So..... which options should be used in the Traccar Client to avoid allowing the app to be shut down by IOS?