Server not receiving updates from Traccar iOS/Apple clients after a while

Hi, first of all thanks for the software. So far it looks amazing and was a breeze to set up. Unsure how well iOS/iPadOS devices are supported. I set up a Traccar server today (LAN only for testing) and the client on 2 iPads. The actual setup went flawlessly, but the server stops receiving location from the 2 devices after a few minutes.

• Traccar Client on both devices has been granted full permissions for always on location services, precise location and app background activity. - The device location shows up almost instantly on the server when the Traccar client app has the location button toggled on (or off and on again)
• All the devices are connected to the same wifi as the Traccar server
• Interval is set to 60s for both interval and stationary heartbeat, location accuracy is "Highest" (should it be something else on iOS?), offline buffering and stop detection are on. Distance is 100m. Everything else is default.
• I'm not swiping the app away after it connects (just swiping up), so it's still in "open" background apps.
• After a while the server stops receiving location updates (e.g last seen 15 mins ago)
• The iOS devices are not being moved around or outside of wifi signal area.

Here is the log below for one of the devices. Is it because I'm not moving them?

2026-09-03 11:41:47 Tracker start [redacted]
2026-09-03 11:41:47 Location updates started
2026-09-03 11:41:47 Motion update: stationary/confidence=0
2026-09-03 11:41:47 Stop detection: arming 60s timeout
2026-09-03 11:41:47 Transition accepted [redacted]
2026-09-03 11:41:47 Location filtered [redacted]
2026-09-03 11:41:47 Location filtered [redacted]
2026-09-03 11:41:47 Upload response 200
2026-09-03 11:41:49 Motion update: none/confidence=2
2026-09-03 11:41:49 Motion update: stationary/confidence=0
2026-09-03 11:41:50 Motion update: none/confidence=2
2026-09-03 11:41:53 Motion update: stationary/confidence=0
2026-09-03 11:41:53 Location filtered [redacted]
2026-09-03 11:41:55 Motion update: none/confidence=2
2026-09-03 11:41:55 Motion update: stationary/confidence=0
2026-09-03 11:41:56 Motion update: none/confidence=2
2026-09-03 11:41:59 Motion update: stationary/confidence=0
2026-09-03 11:42:01 Location filtered [redacted]
2026-09-03 11:42:02 Motion update: stationary/confidence=0
2026-09-03 11:42:03 Motion update: stationary/confidence=2
2026-09-03 11:42:16 Location filtered [redacted]
2026-09-03 11:42:31 Location filtered [redacted]
2026-09-03 11:42:46 Location accepted [redacted]
2026-09-03 11:42:46 Upload response 200
2026-09-03 11:42:47 StationaryEnter: pausing
2026-09-03 11:42:47 Heartbeat scheduled in 60s
2026-09-03 11:42:57 Location updates stopped
2026-09-03 11:42:57 Region monitoring registered
2026-09-03 12:25:29 Motion update: stationary/confidence=0
2026-09-03 12:25:29 Stop detection: arming 60s timeout
2026-09-03 12:25:30 Motion update: stationary/confidence=0
2026-09-03 12:25:31 Motion update: stationary/confidence=2
2026-09-03 12:25:36 Motion update: stationary/confidence=2

Thanks for the logs - that pins it down. Once the device stops moving, the client stops active GPS and switches to periodic heartbeats scheduled via iOS's BGAppRefreshTask. The interval you set (60s) is only a minimum - iOS decides when to actually run it, based on app usage, battery, etc., and can delay it by many minutes regardless of what you configure. That's a platform limitation, not something the app can force.

Since your devices aren't moving or leaving the area, there's nothing else that would trigger an update in between - the heartbeat is the only possible source while stationary, so the gap you're seeing matches how late iOS ran that background task, not a bug in the client or server.