IOS client 9.6.5 stopped tracking
While an entry is still created in the logs when this action is performed, no actual update occurs.
What do you mean exactly? Because the log shows the update.
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 0.0m | age: 85 ms
╚═══════════════════════════════════════════════════════════
2025-12-27 21:50:45.085
<+47.12560470,+12.65150039> +/- 4.75m (speed 0.00 mps / course 119.44) @ 27.12.25, 21:50:44 Central European Standard Time
2025-12-27 21:50:44.099 -[LocationDAO destroyByUuid:]_block_invoke DESTROY: D8994CAE-6CA2-4991-A661-AECA77F62755
2025-12-27 21:50:44.096 -[TSLocationManager persistLocation:]_block_invoke INSERT: D8994CAE-6CA2-4991-A661-AECA77F62755
2025-12-27 21:50:44.086 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 4.7
2025-12-27 21:50:44.086
but the issue ist that er is no more updates in the UI since days or only very sporadic - so no way tracking
So is it no updates or sporadic updates? Do you see regular updates in the log? You keep providing contradicting information.
after some time the UI shows offline - and when I press “Send location” than UI changes to online
but no changes of the shown date - in this case I still see in the Web UI - myPhone, time: 2025-12-27 21:30:14, lat: 47.12569, lon: 12.65155, speed: 5.6, course: 359.8
but the Iphone is on an other location and there is no movement - I have changes the location for more than 200 meter
Have you checked all permissions? Have you tried reinstalling the app?
Yes - deletet Traccar Cllient App and reinstalling
also reboot the iPhone
Was there some iOS update?
Iphone is on 26.2 but update has done more than 2 weeks ago - I have also checked all APP configs
like Background update, mobil data, location,... - no changes and full access
sorry for delay the forum shows allways to many requests
In the APP Log I see the movement because GEO Data are changing but no update in UI because Server log shows still old Geo data
Server LOG:
2025-12-27 23:20:11 INFO: [Td9d1c50c: osmand < 80.187.71.162] POST / HTTP/1.1\r\nHost: track.test:5055\r\nContent-Type: application/json; charset=utf-8\r\nConnection: keep-alive\r\nAccept: */*\r\nUser-Agent: traccar_client/113 CFNetwork/3860.300.31 Darwin/25.2.0\r\nContent-Length: 449\r\nAccept-Language: de-DE,de;q=0.9\r\nAccept-Encoding: gzip, deflate\r\n\r\n{"location":{"coords":{"heading":84.549999999999997,"speed":0,"latitude":47.125594383811368,"longitude":12.65149521440555,"accuracy":4.75,"altitude":466.06},"extras":{},"is_moving":true,"_":"&id=myPhone&lat=47.12559438381137&lon=12.65149521440555×tamp=2025-12-27T20:40:46.999Z&","odometer":24577.599999999999,"activity":{"type":"still"},"battery":{"level":0.75,"is_charging":false},"timestamp":"2025-12-27T20:40:46.999Z"},"device_id":"myPhone"}
2025-12-27 23:20:11 INFO: [Td9d1c50c: osmand > 80.187.71.162] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2025-12-27 23:20:13 INFO: [Td9d1c50c] disconnected
2025-12-27 23:20:14 INFO: [Td9d1c50c] id: myPhone, time: 2025-12-27 21:40:46, lat: 47.12559, lon: 12.65150, course: 84.6
App Log (this was during the drive 2 hours ago):
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 0.0m | age: 81 ms
╚═══════════════════════════════════════════════════════════
2025-12-27 21:31:30.081
<+47.12563580,+12.65163460> +/- 4.75m (speed 1.02 mps / course 70.47) @ 27.12.25, 21:31:30 Central European Standard Time
2025-12-27 21:31:29.091 -[TSLocationManager persistLocation:]_block_invoke INSERT: 9E699169-C075-4CAE-8CED-A7D3B4B7AA26
2025-12-27 21:31:29.085 -[TSHttpService flush:failure:] Busy with previous request
2025-12-27 21:31:29.085 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-27 21:31:29.081 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 4.7
2025-12-27 21:31:29.081
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 0.0m | age: 81 ms
╚═══════════════════════════════════════════════════════════
2025-12-27 21:31:29.081
<+47.12563676,+12.65161283> +/- 4.75m (speed 0.81 mps / course 43.16) @ 27.12.25, 21:31:29 Central European Standard Time
2025-12-27 21:31:28.094 -[LocationDAO destroyByUuid:]_block_invoke DESTROY: 3F3EEF06-638B-40BC-BEDE-91910E6EB77D
2025-12-27 21:31:28.091 -[TSLocationManager persistLocation:]_block_invoke INSERT: 3F3EEF06-638B-40BC-BEDE-91910E6EB77D
2025-12-27 21:31:28.087 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 4.7
2025-12-27 21:31:28.087
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 0.0m | age: 86 ms
╚═══════════════════════════════════════════════════════════
2025-12-27 21:31:28.087
<+47.12562752,+12.65159125> +/- 4.75m (speed 0.40 mps / course 29.79) @ 27.12.25, 21:31:28 Central European Standard Time
2025-12-27 21:31:27.090 -[LocationDAO destroyByUuid:]_block_invoke DESTROY: FBF1CE73-E516-4929-B8C7-87C5CF0B9CB7
2025-12-27 21:31:27.088 -[TSLocationManager persistLocation:]_block_invoke INSERT: FBF1CE73-E516-4929-B8C7-87C5CF0B9CB7
2025-12-27 21:31:27.084 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 4.7
2025-12-27 21:31:27.084
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 0.0m | age: 84 ms
╚═══════════════════════════════════════════════════════════
2025-12-27 21:31:27.084
<+47.12562254,+12.65158493> +/- 4.75m (speed 0.06 mps / course 15.22) @ 27.12.25, 21:31:27 Central European Standard Time
2025-12-27 21:31:26.155 -[TSHttpService init]_block_invoke Network: WiFi | Flags: -R -t-----
2025-12-27 21:31:26.092 -[LocationDAO destroyByUuid:]_block_invoke DESTROY: CB699FBB-973A-459E-B843-83EF7549180F
2025-12-27 21:31:26.087 -[TSLocationManager persistLocation:]_block_invoke INSERT: CB699FBB-973A-459E-B843-83EF7549180F
2025-12-27 21:31:26.081 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 4.7
Sorry for delay forum showing to many requests
iPhone is on 26.2 but has updated more than 2 weeks ago
App config has checked like access to location, background update or mobile data have full access
Based on the app log, it seems like the location on the phone is updating. Not sure why it's not sent.
I'm getting the same issue on an android where the apps logs show the location being updated and sent but it's not actually being reflected in the manager. I took a trip to Edinburgh with three traccar clients on three separate android phones. Two of the clients returned south fine, but the third one is still in Edinburgh. I can see on server logs that it's receiving the correct location and current date ect. when the manual location send button is pressed but this is not being displayed on traccar manager.
The affected phone is a pixel 7 pro with the latest updates.
It doesn't sound like the same issue.
Hello Anton thanks for support
This topic remains confusing for me as well. Today, I again completed a 200 km trip to further investigate the issue.
According to the app logs (snippet around 18:20), the GeoData appears to have been updated correctly. However, at the same time, the server logs show an outdated request containing old GeoData and an old timestamp (11:36). This discrepancy is difficult to explain.
From a non-professional perspective, it looks as though the client may be retrieving data from a cache and then sending that cached data to the server.
My initial assumption was that this might be related to offline buffering. However, I tested this extensively during today’s drive, with offline buffering both enabled and disabled, and the behavior did not change. I also tested with an Android device during the same trip, which worked without any issues. Based on this, I am currently ruling out a problem with the server, domain, port, or general backend configuration.
Additionally, I stopped during the trip and manually tested connectivity to the domain, which worked as expected. This leads me to also exclude mobile data connectivity as the root cause.
At this point, I am unsure what else to test. The issue started on December 24th at approximately 9:45 PM, without any updates to the app, the iPhone, or the server around that time. The only remaining explanation I can think of is an undocumented change introduced by Apple.
Server Log:
2025-12-28 18:20:11 INFO: [T125e3f55] connected
2025-12-28 18:20:11 INFO: [T125e3f55: osmand < 80.187.70.15] POST / HTTP/1.1\r\nHost: track.test.de:5055\r\nContent-Type: application/json; charset=utf-8\r\nConnection: keep-alive\r\nAccept: */*\r\nUser-Agent: traccar_client/113 CFNetwork/3860.300.31 Darwin/25.2.0\r\nContent-Length: 465\r\nAccept-Language: de-DE,de;q=0.9\r\nAccept-Encoding: gzip, deflate\r\n\r\n{"location":{"coords":{"heading":205,"speed":22.739999999999998,"latitude":46.104342272985328,"longitude":12.65022607185551,"accuracy":4.75,"altitude":504.04000000000002},"extras":{},"is_moving":true,"_":"&id=myPhone&lat=46.10434227298533&lon=12.65022607185551×tamp=2025-12-28T10:36:30.000Z&","odometer":28567.299999999999,"activity":{"type":"in_vehicle"},"battery":{"level":1,"is_charging":false},"timestamp":"2025-12-28T10:36:30.000Z"},"device_id":"myPhone"}
2025-12-28 18:20:11 INFO: [T125e3f55: osmand > 80.187.70.15] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2025-12-28 18:20:13 INFO: [T125e3f55] disconnected
2025-12-28 18:20:14 INFO: [T125e3f55] id: myPhone, time: 2025-12-28 11:36:30, lat: 46.10434, lon: 12.65023, speed: 44.2, course: 205.0
APP Log:
2025-12-28 18:20:05.083
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 83 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:20:05.083
<+46.29562241,+11.57770842> +/- 2.01m (speed 31.99 mps / course 233.55) @ 28.12.25, 18:20:05 Central European Standard Time
2025-12-28 18:20:04.095 -[TSLocationManager persistLocation:]_block_invoke INSERT: 3DD0E4FC-60E5-488F-9FD9-E04C19F7B967
2025-12-28 18:20:04.088 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:20:04.088 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:20:04.084 -[TSConfig incrementOdometer:] 268692.8
2025-12-28 18:20:04.080 -[TSConfig persist]
2025-12-28 18:20:04.080 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.0
2025-12-28 18:20:04.080
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 80 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:20:04.080
<+46.29579053,+11.57805744> +/- 2.22m (speed 31.83 mps / course 233.54) @ 28.12.25, 18:20:03 Central European Standard Time
2025-12-28 18:20:03.096 -[TSLocationManager persistLocation:]_block_invoke INSERT: 34542EC9-EF52-44F5-BBA6-C479B047F856
2025-12-28 18:20:03.088 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:20:03.088 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:20:03.085 -[TSConfig incrementOdometer:] 268660.9
2025-12-28 18:20:03.081 -[TSConfig persist]
2025-12-28 18:20:03.081 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.1
2025-12-28 18:20:03.081
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 81 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:20:03.081
<+46.29595844,+11.57840584> +/- 2.01m (speed 31.59 mps / course 233.46) @ 28.12.25, 18:20:02 Central European Standard Time
2025-12-28 18:20:02.099 -[TSLocationManager persistLocation:]_block_invoke INSERT: 304EE5C4-C79A-4195-9D5B-B86F43224B2A
2025-12-28 18:20:02.092 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:20:02.092 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:20:02.088 -[TSConfig incrementOdometer:] 268629.3
2025-12-28 18:20:02.085 -[TSConfig persist]
2025-12-28 18:20:02.085 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.0
2025-12-28 18:20:02.085
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 84 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:20:02.085
<+46.29612434,+11.57875113> +/- 2.16m (speed 31.40 mps / course 233.52) @ 28.12.25, 18:20:01 Central European Standard Time
2025-12-28 18:20:01.098 -[TSLocationManager persistLocation:]_block_invoke INSERT: BEE0802F-F537-4A7E-B382-AB269F64CD33
2025-12-28 18:20:01.091 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:20:01.091 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:20:01.087 -[TSConfig incrementOdometer:] 268598.0
2025-12-28 18:20:01.085 -[TSConfig persist]
2025-12-28 18:20:01.085 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.0
2025-12-28 18:20:01.085
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 85 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:20:01.084
<+46.29628862,+11.57909388> +/- 2.00m (speed 31.21 mps / course 233.47) @ 28.12.25, 18:20:00 Central European Standard Time
2025-12-28 18:20:00.091 -[TSLocationManager persistLocation:]_block_invoke INSERT: 6901224B-EBB7-4D00-B56B-399006040AA1
2025-12-28 18:20:00.085 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:20:00.085 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:20:00.082 -[TSConfig incrementOdometer:] 268566.9
2025-12-28 18:20:00.079 -[TSConfig persist]
2025-12-28 18:20:00.079 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.0
2025-12-28 18:20:00.079
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 79 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:20:00.079
<+46.29645218,+11.57943447> +/- 2.01m (speed 31.03 mps / course 233.40) @ 28.12.25, 18:19:59 Central European Standard Time
2025-12-28 18:19:59.096 -[TSLocationManager persistLocation:]_block_invoke INSERT: D9764D7F-338E-4BE5-A284-0766C5DB4154
2025-12-28 18:19:59.090 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:19:59.089 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:19:59.085 -[TSConfig incrementOdometer:] 268536.0
2025-12-28 18:19:59.083 -[TSConfig persist]
2025-12-28 18:19:59.082 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.3
2025-12-28 18:19:59.082
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 82 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:19:59.082
<+46.29661538,+11.57977150> +/- 2.01m (speed 30.85 mps / course 233.23) @ 28.12.25, 18:19:58 Central European Standard Time
2025-12-28 18:19:58.096 -[TSLocationManager persistLocation:]_block_invoke INSERT: 596A0B6A-462A-40C4-B79E-65D7EC28A701
2025-12-28 18:19:58.089 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:19:58.089 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:19:58.085 -[TSConfig incrementOdometer:] 268505.2
2025-12-28 18:19:58.082 -[TSConfig persist]
2025-12-28 18:19:58.082 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.5
2025-12-28 18:19:58.082
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 82 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:19:58.082
<+46.29677747,+11.58010690> +/- 2.14m (speed 30.69 mps / course 233.24) @ 28.12.25, 18:19:57 Central European Standard Time
2025-12-28 18:19:57.095 -[TSLocationManager persistLocation:]_block_invoke INSERT: 17339325-089B-4EF2-97B2-0ABE82D1631F
2025-12-28 18:19:57.088 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:19:57.088 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:19:57.084 -[TSConfig incrementOdometer:] 268474.6
2025-12-28 18:19:57.081 -[TSConfig persist]
2025-12-28 18:19:57.081 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.4
2025-12-28 18:19:57.081
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 81 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:19:57.081
<+46.29693949,+11.58044016> +/- 2.00m (speed 30.71 mps / course 233.44) @ 28.12.25, 18:19:56 Central European Standard Time
2025-12-28 18:19:56.091 -[TSLocationManager persistLocation:]_block_invoke INSERT: B5959145-2FD7-4873-8885-448C6C68ADDF
2025-12-28 18:19:56.084 -[TSHttpService flush:failure:] Busy with previous request
2025-12-28 18:19:56.084 -[TSLocationManager sync:failure:] Manual HTTP sync: Network available? 1 | HttpService busy? 1
2025-12-28 18:19:56.080 -[TSConfig incrementOdometer:] 268444.0
2025-12-28 18:19:56.076 -[TSConfig persist]
2025-12-28 18:19:56.076 -[TSLocationManager calculateMedianLocationAccuracy:] Median location accuracy: 2.5
2025-12-28 18:19:56.076
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager locationManager:didUpdateLocations:] Enabled: 1 | isMoving: 1 | df: 5.0m | age: 76 ms
╚═══════════════════════════════════════════════════════════
2025-12-28 18:19:56.076
<+46.29710171,+11.58077465> +/- 2.01m (speed 30.67 mps / course 233.51) @ 28.12.25, 18:19:55 Central European Standard Time
2025-12-28 18:19:55.713
╔═══════════════════════════════════════════════════════════
║ -[TSLocationManager createMotionTypeChangedHandler]_block_invoke | in_vehicle/100 | isMoving: 1
╚═══════════════════════════════════════════════════════════
2025-12-28 18:19:55.095 -[TSLocationManager persistLocation:]_block_invoke INSERT: 2CCA108F-3F86-4361-BC2C-662FC558DC97
Dear Traccar Team,
For the past two days (since 24.12 at approximately 21:45), I have observed unexpected behavior in my installation.
Without any configuration changes or updates—neither on the server side nor in the mobile app—location tracking on an iPhone 17 Pro has stopped working.
The system is currently running Server version 6.11.1 and App version 9.6.5, which are the latest available versions.
To troubleshoot the issue, I verified the configuration and system settings and also performed a complete reinstallation and new setup on the affected iPhone. However, the problem persists. An Android device connected to the same server continues to work correctly, which suggests that the issue is isolated to iOS.
Previously, when using the “Send location” function, the location and all related data were updated immediately. While an entry is still created in the logs when this action is performed, no actual update occurs. It appears that the request sent to the server contains outdated data.
Please find the relevant log entries attached below for reference. (Server URL hast changed for Data Privacy reasons)
IOS APP Config:
Server Log: