Traccar Client Troubleshooting

Tap "Show status" to open the Logs screen in the Traccar Client app:

• "Location accepted" or "Transition accepted" means a location has passed the app's filter. It does not confirm that the server received it.
• If you see "Location filtered", "StationaryEnter: pausing", or no new locations, proceed to point 2.
• If you see "Upload error", "Upload failed, retrying", "Offline, waiting for network", or an "Upload response" outside the 200–299 range, proceed to point 3.
• An "Upload response" in the 200–299 range means the HTTP endpoint accepted the request. If no data appears on your server, check the server URL, device identifier, and server logs.

If the application stops working after some time, check point 6.

Missing reports do not always mean that the operating system has stopped providing locations. Check the tracking state and settings first:

• Make sure "Continuous tracking" is enabled. If tracking fails to start, check location permissions in system settings.
• "Location updates started" means the app requested updates, not that it has received a location fix.
• "Location filtered" means a location was received but did not meet the reporting thresholds. Review Distance, Interval, and Angle in the configuration guide.
• "StationaryEnter: pausing" means stop detection paused regular location updates. Stop detection is enabled by default, and Stationary heartbeat is disabled by default. Move the device to test resuming, configure a Stationary heartbeat, or disable Stop detection in Advanced settings if you need tracking to remain active while stationary.
• Tap "Send location" to test a manual report. "Position fetched" means a location was obtained; check the following upload result. "Position request: no fix" means the app could not obtain a location.
• If Location accuracy is Medium or Low, check point 4. If it is High or Highest, check point 5.

"Upload error" indicates a failed request. "Upload response" shows the HTTP status returned by the endpoint; only 200–299 responses count as successful uploads. Check the following:

• Register the app's Device identifier as the device's unique identifier on the server. Make sure they match exactly.
• Network connection issues on your mobile device. Check network connectivity.
• Use a full Server URL, including http:// or https:// and the correct port. The default Traccar Client protocol port is 5055; use the address configured for receiving client reports, which may differ from the web interface address.
• Some other server issue. Try server troubleshooting guide.

With Offline buffering enabled, continuous tracking stores reports locally, waits for connectivity, and retries failed uploads. "Offline, waiting for network" and "Upload failed, retrying" explain why accepted locations have not reached the server yet. With buffering disabled, failed reports are dropped. Manual "Send location" reports are uploaded directly and are not buffered.

Medium (default) and Low request less accurate locations to reduce power use. They do not always select a specific location provider:

• On Android, the app normally uses Google's Fused Location Provider when Google Play Services is available. Medium requests balanced accuracy and Low requests low power usage.
• If Google Play Services is unavailable or "Use system location" is enabled in Advanced settings, Medium prefers the network provider and Low prefers the passive provider. Passive locations depend on updates requested by other apps and may be infrequent. The app falls back to an available provider if the preferred provider is absent.
• On iOS, Medium requests approximately 100-meter accuracy and Low requests kilometer accuracy. The operating system chooses the location sources.
• Check that location services and app location permissions are enabled. For network-based positioning, also check connectivity and Wi-Fi availability.
• If locations are unavailable or too imprecise, try High or Highest accuracy and test outdoors.

High and Highest request more accurate locations, typically using GPS. On Android, both request high accuracy from the fused provider, or prefer GPS when using system providers. On iOS, High requests the best available accuracy and Highest requests navigation accuracy.

• Test outdoors with a clear view of the sky and allow time for a GPS fix. Buildings and indoor locations can weaken or block satellite signals.
• Check that location services are enabled and the app has precise location permission.
• Highest changes how the app requests updates, but reporting thresholds and stop detection still apply. Check point 2 if updates are filtered or tracking is paused.

Background restrictions can interrupt tracking. First check point 2 to rule out normal stationary behavior, then check the following:

• On iOS, if you swipe the app off the screen, the operating system actually kills the process, and the app will no longer be able to report.
• Make sure that in iOS settings background execution is allowed and Traccar Client has permission to always access location services.
• On Android, allow precise location and background location access. Also check Physical activity permission, which the app uses for stop detection.
• On recent versions of Android make sure that you have added Traccar Client to battery optimization exceptions.
• Some Android vendors have their own battery optimization in addition to the standard Android system. Make sure those are disabled or the app is added to exceptions.
• Check the Don't Kill My App website for more vendor-specific details.

If you still have issues, open "Show status" and use the share button to export logs.txt. Include the app version, phone model, operating system version, and relevant settings when reporting the issue. Collect operating system logs as well if the app logs do not explain the problem.