IoS Client 10.2.4 Update sent with stale location

ZuluBravo 16 hours ago

I have observed a number of devices reporting in with stale fix data. It's happening across multiple IOS devices with latest IOS versions and multiple device types. I can see in both the traccar server log and in the DB that the client is uploading only stale fix data. In this case very latent (months old) data so it's likely not a server side issue. I am running 6.16 on the server side and 10.2.4 on the client. No errors are present in the server of client logs.

Here is an example of what I am seeing in the DB logs:

ServerTime DeviceTime FixTime
2026-11-04 16:44:44 2026-11-04 16:44:44 2026-05-30 16:46:36

Is this a known issue? Has anyone else encountered this? Is there any way to debug this issue?

Anton Tananaev 15 hours ago

Have you checked client logs? That would obviously be the first step for debugging something like this.

ZuluBravo 14 hours ago

Here is what I am seeing on the server (sanitized) I do see a socket exception. Not much other context than that.

2026-11-09 18:02:19  INFO: [T03efa3ff] connected
2026-11-09 18:02:19  INFO: [T03efa3ff: osmand < 1.2.3.4] POST / HTTP/1.1\r\nuser-agent: Dart/3.13 (dart:io)\r\ncontent-type: application/x-www-form-urlencoded\r\ntransfer-encoding: chunked\r\naccept-encoding: gzip\r\nhost: internet.server.local:5055\r\n\r\n34\r\nid=client12345&notificationToken=xyz\r\n0\r\n\r\n
2026-11-09 18:02:19  INFO: [T03efa3ff: osmand > 1.2.3.4] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2026-11-09 18:02:21  INFO: [T0cfb28e0] connected
2026-11-09 18:02:21  INFO: [T0cfb28e0: osmand < 1.2.3.4] POST / HTTP/1.1\r\nHost: internet.server.local:5055\r\nContent-Type: application/x-www-form-urlencoded; charset=UTF-8\r\nConnection: keep-alive\r\nAccept: */*\r\nUser-Agent: ktor-client\r\nContent-Length: 138\r\nAccept-Language: en-US,en;q=0.9\r\nAccept-Encoding: gzip, deflate\r\n\r\nid=client12345&lat=311&lon=-22&timestamp=1794276139&accuracy=5.0&altitude=100.00&batt=75&charge=false
2026-11-09 18:02:21  INFO: [T0cfb28e0: osmand > 1.2.3.4] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2026-11-09 18:02:24  INFO: [T03efa3ff] id: client12345, time: 2026-10-30 18:47:13, lat: 11, lon: -22, course: 0.0, accuracy: 167.3
2026-11-09 18:02:24  INFO: [T0cfb28e0] id: client12345, time: 2026-11-09 18:02:19, lat: 11, lon: -22, course: 0.0, accuracy: 5.0
2026-11-09 18:02:24  INFO: [T0cfb28e0: osmand < 1.2.3.4] POST / HTTP/1.1\r\nHost: internet.server.local:5055\r\nContent-Type: application/x-www-form-urlencoded; charset=UTF-8\r\nConnection: keep-alive\r\nAccept: */*\r\nUser-Agent: ktor-client\r\nContent-Length: 138\r\nAccept-Language: en-US,en;q=0.9\r\nAccept-Encoding: gzip, deflate\r\n\r\nid=client12345&lat=11&lon=-22&timestamp=1794276141&accuracy=5.0&altitude=100&batt=75&charge=false
2026-11-09 18:02:24  INFO: [T0cfb28e0: osmand > 1.2.3.4] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2026-11-09 18:02:27  WARN: [T0cfb28e0] error - Connection reset - SocketException (...)
2026-11-09 18:02:27  INFO: [T0cfb28e0] disconnected
2026-11-09 18:02:28  INFO: [T0cfb28e0] id: client12345, time: 2026-11-09 18:02:21, lat: 11, lon: -22, course: 0.0, accuracy: 5.0

Anton Tananaev 14 hours ago

Wrong logs.

ZuluBravo 14 hours ago

There isnt anything obvious in the client logs from what I can tell. I am seeing 200's on the server after periodic uploads. Perhaps the socket exception is the key and the upload of multiple records is failing?

Here is the last few hours of the log.

2026-10-30 08:27:06 Location filtered 11,22
2026-10-30 08:27:06 Location filtered 11,22
2026-10-30 08:27:06 Motion update: none/confidence=2
2026-10-30 08:27:09 Location filtered 11,22
2026-10-30 08:27:09 Motion update: stationary/confidence=0
2026-10-30 08:27:13 Motion update: none/confidence=2
2026-10-30 08:27:13 Motion update: stationary/confidence=0
2026-10-30 08:27:14 StationaryEnter: pausing
2026-10-30 08:27:14 Motion update: none/confidence=2
2026-10-30 08:27:15 Transition accepted 11,22
2026-10-30 08:27:15 Region monitoring registered
2026-10-30 08:27:15 Location updates stopped
2026-10-30 08:27:15 Location filtered 11,22
2026-10-30 08:27:16 Upload response 200
2026-10-30 08:27:36 Motion update: none/confidence=2
2026-10-30 08:27:39 Motion update: none/confidence=2
...
2026-10-30 18:46:47 Motion update: none/confidence=2
2026-10-30 18:46:50 Location accepted 11,22
2026-10-30 18:46:50 Upload response 200
2026-10-30 18:46:51 Location filtered 11,22
2026-10-30 18:46:52 Location accepted 11,22
2026-10-30 18:46:52 Upload response 200
2026-10-30 18:46:53 Location filtered 11,22
2026-10-30 18:46:54 Location filtered 11,22
2026-10-30 18:46:55 Location filtered 11,22
2026-10-30 18:47:00 Location accepted 11,22
2026-10-30 18:47:00 Upload response 200
2026-10-30 18:47:02 Location accepted 11,22
2026-10-30 18:47:02 Upload response 200
2026-10-30 18:47:02 Location filtered 11,22
2026-10-30 18:47:06 Location filtered 11,22
2026-10-30 18:47:08 Motion update: stationary/confidence=0
2026-10-30 18:47:09 Motion update: none/confidence=2
2026-10-30 18:47:13 Location accepted 11,22
2026-10-30 18:47:13 Location filtered 11,22
2026-10-30 18:47:14 Upload response 200
2026-10-30 18:47:16 Location filtered 11,22
2026-10-30 18:47:16 Location filtered 11,22
2026-10-30 18:47:20 StationaryEnter: pausing
2026-10-30 18:47:30 Location updates stopped
2026-10-30 18:47:30 Region monitoring registered
2026-11-09 19:02:18 Network online
2026-11-09 19:02:18 Motion update: none/confidence=2
2026-11-09 19:02:21 Position requested
2026-11-09 19:02:21 Position fetched 11,22
2026-11-09 19:02:21 Motion update: stationary/confidence=0
2026-11-09 19:02:21 Stop detection: arming 60s timeout
2026-11-09 19:02:21 Upload response 200
2026-11-09 19:02:21 Motion update: none/confidence=2
2026-11-09 19:02:22 Motion update: stationary/confidence=0
2026-11-09 19:02:23 Motion update: none/confidence=2
2026-11-09 19:02:23 Motion update: stationary/confidence=0
2026-11-09 19:02:23 Motion update: none/confidence=2
2026-11-09 19:02:24 Position requested
2026-11-09 19:02:24 Position fetched 11,22
2026-11-09 19:02:24 Upload response 200
2026-11-09 19:14:52 Network online
2026-11-09 19:14:52 Motion update: none/confidence=2
2026-11-09 19:14:52 Motion update: none/confidence=2
2026-11-09 19:14:54 Motion update: stationary/confidence=0
2026-11-09 19:14:54 Stop detection: arming 60s timeout

Anton Tananaev 12 hours ago

I don't think socket error is a problem. On the client side we see that positions are accepted. So I don't see any obvious issues. Your phone must be reporting outdated location or incorrect time.