Major Traccar Client update

Anton Tananaev 23 days ago

Thanks for testing. Heartbeat is supported in this new version:

https://traccar.nyc3.digitaloceanspaces.com/download/app-release.apk

I think we're getting very close to official release.

Antony 23 days ago

The most recent apk doesn't get installed on any of my devices whether with play services or without it

Anton Tananaev 23 days ago

What's the error?

Antony 23 days ago

It just says "App not installed as package appear to be invalid" .

AussieTraccar 23 days ago

Upgraded fine on my Google Play Android 13 device and non-Google Play Android 12 device.

Thank you for adding in "Send SOS" support into this pre-release.

Andrew M 23 days ago

My testing with the new iPhone client has gone well but I've only tested it in detail on Highest accuracy setting.
Hopefully I won't need to review the logs very often but it might be useful to log the active settings, eg with the 'Tracker start ' message.

Antony 23 days ago

I think a new apk was released as it has a different hash to the one that wasn't installing for me and now it installs fine . Deeplinking for the heartbeat is missing btw in this version

Anton Tananaev 22 days ago

Thanks everyone for testing and feedback. Here's hopefully the last build before official release.

Android: https://traccar.nyc3.digitaloceanspaces.com/download/app-release.apk
iOS: https://testflight.apple.com/join/jz3jvbnw

Please give it a go and provide feedback. It should not be very different, but there were some missing pieces in older versions, like it wasn't respecting buffering and stop detection switches.

Deeplink for heartbeat will be fixed in the next build.

Andrew M 22 days ago

Thanks Anton, great work.

I was recording a walk yesterday and during a period of little movement I got the following in the log.
Does this (eg 'StationaryEnter') reflect 'Stop Detection'? It was enabled.

24/06/2026 15:25	Location filtered [lat,lon]
24/06/2026 15:25	StationaryEnter: pausing
24/06/2026 15:25	Transition accepted [lat,lon]
24/06/2026 15:25	Region monitoring registered
24/06/2026 15:25	Location filtered [lat,lon]
24/06/2026 15:25	Location updates stopped
24/06/2026 16:24	Region exit
24/06/2026 16:24	StationaryExit: resuming
24/06/2026 16:24	Heartbeat task cancelled
24/06/2026 16:24	Location updates started
24/06/2026 16:24	Region monitoring removed
24/06/2026 16:24	Motion update: walking/confidence=2
24/06/2026 16:24	Transition accepted [lat,lon]
24/06/2026 16:24	Location filtered [lat,lon]
Anton Tananaev 22 days ago

Yes, that's stop detection.

Antony 22 days ago

If the app was killed from ram and the user tap on intent button to configure traccar. The "Apply new configuration" popup will show up twice

Anton Tananaev 21 days ago

Thanks. Another legit bug. It is unrelated to the new app, but will be fixed in the next version.

Antony 20 days ago

Can you please consider adding the last known coordinates to the posted data for the heartbeat?

The reason is, if the user was at location X and lost internet connection with offline buffering turned off and started moving till they reached point Y then got internet connection while they are in stationary mode in location Y. Since the heartbeat no longer has the coordinates, the server will still think they are in point X

Anton Tananaev 19 days ago

Not sure I understand the explanation. The client should first upload buffered coordinates when it gets online.

Antony 19 days ago

That will work too, but was wondering if the coordinates can be included in the heartbeat data.

Here is an example of why including the coordinates in the heartbeat request would be useful.

Consider this real-world scenario:

A user is stationary at Location X, and the server correctly knows their position. The user then starts moving away from Location X but loses internet connectivity because they leave Wi-Fi coverage and have mobile data turned off.

Since offline buffering is disabled, none of the location updates generated while the user is moving can be sent to the server. As far as the server is concerned, the user is still at Location X.

Eventually, the user arrives at Location Y and reconnects to Wi-Fi. By that time, traccar has already switched back to stationary mode, so it only sends heartbeat requests. Those heartbeat requests indicate that the device is online again, but they do not include the current coordinates. As a result, the server still believes the user is at Location X, even though they are now at Location Y.

If the heartbeat request included the current coordinates, the server would update the user's location as soon as connectivity is restored, even if all intermediate location updates were missed.