Not uploading stored location info

Hi Anton,
I had installed traccar client on an IOS device with no internet connection..when I am located under wifi coverage it works perfectly, when I go out of wifi zone just as is expected it do not update location info until I return back to wifi covergade.......
I had 2 issues :
1-It does not upload offline route (I understood that it should upload stored location info, right?) and
2- It is showing a IO exception error...No idea..could you please give me some hints?

Here under some info from log.

2018-12-10 13:33:39 DEBUG: [2C6B62D6: 5055 < 179.18.38.220] HEX: 504f5354202f3f69643d3138303332382674696d657374616d703d31353434343633363430266c61743d342e383637333838266c6f6e3d2d37342e3036333138322673706565643d312e37383833333238333234343133332662656172696e673d3231362e3231303933373526616c7469747564653d323535322e363037393130313536323526626174743d373220485454502f312e310d0a486f73743a203136322e3231332e3132312e3232333a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35302043464e6574776f726b2f3930322e322044617277696e2f31372e372e300d0a4163636570742d4c616e67756167653a2065732d65730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2018-12-10 13:33:39 DEBUG: [2C6B62D6: 5055 > 179.18.38.220] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-12-10 13:33:39  INFO: [2C6B62D6] id: 180328, time: 2018-12-10 12:40:40, lat: 4.86739, lon: -74.06318, speed: 1.8, course: 216.2
2018-12-10 13:33:39  WARN: [2C6B62D6] error - An existing connection was forcibly closed by the remote host - IOException (...)
2018-12-10 13:33:39  INFO: [2C6B62D6] disconnected

2018-12-10 13:38:19 DEBUG: [EAD5E893: 5055 < 179.18.38.220] HEX: 504f5354202f3f69643d3138303332382674696d657374616d703d31353434343633363430266c61743d342e383637333838266c6f6e3d2d37342e3036333138322673706565643d312e37383833333238333234343133332662656172696e673d3231362e3231303933373526616c7469747564653d323535322e363037393130313536323526626174743d373220485454502f312e310d0a486f73743a203136322e3231332e3132312e3232333a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35302043464e6574776f726b2f3930322e322044617277696e2f31372e372e300d0a4163636570742d4c616e67756167653a2065732d65730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2018-12-10 13:38:19 DEBUG: [EAD5E893: 5055 > 179.18.38.220] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-12-10 13:38:19  WARN: [EAD5E893] error - An existing connection was forcibly closed by the remote host - IOException (...)
2018-12-10 13:38:19  INFO: [EAD5E893] disconnected
2018-12-10 13:38:20  INFO: [EAD5E893] id: 180328, time: 2018-12-10 12:40:40, lat: 4.86739, lon: -74.06318, speed: 1.8, course: 216.2
2018-12-10 13:38:50 DEBUG: [A137FD9B: 5055 < 179.18.38.220] HEX: 504f5354202f3f69643d3138303332382674696d657374616d703d31353434343633363430266c61743d342e383637333838266c6f6e3d2d37342e3036333138322673706565643d312e37383833333238333234343133332662656172696e673d3231362e3231303933373526616c7469747564653d323535322e363037393130313536323526626174743d373220485454502f312e310d0a486f73743a203136322e3231332e3132312e3232333a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35302043464e6574776f726b2f3930322e322044617277696e2f31372e372e300d0a4163636570742d4c616e67756167653a2065732d65730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2018-12-10 13:38:50 DEBUG: [A137FD9B: 5055 > 179.18.38.220] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-12-10 13:39:21 DEBUG: [F44FBC2E: 5055 < 179.18.38.220] HEX: 504f5354202f3f69643d3138303332382674696d657374616d703d31353434343633363430266c61743d342e383637333838266c6f6e3d2d37342e3036333138322673706565643d312e37383833333238333234343133332662656172696e673d3231362e3231303933373526616c7469747564653d323535322e363037393130313536323526626174743d373220485454502f312e310d0a486f73743a203136322e3231332e3132312e3232333a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35302043464e6574776f726b2f3930322e322044617277696e2f31372e372e300d0a4163636570742d4c616e67756167653a2065732d65730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2018-12-10 13:39:21 DEBUG: [F44FBC2E: 5055 > 179.18.38.220] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-12-10 13:39:21  WARN: [F44FBC2E] error - An existing connection was forcibly closed by the remote host - IOException (...)
2018-12-10 13:39:21  INFO: [F44FBC2E] disconnected

Decode

POST /?id=180328×tamp=1544463640&lat=4.867388&lon=-74.063182&speed=1.78833283244133&bearing=216.2109375&altitude=2552.60791015625&batt=72 HTTP/1.1
Host: 162.213.121.223:5055
Connection: keep-alive
Accept: */*
User-Agent: TraccarClient/50 CFNetwork/902.2 Darwin/17.7.0
Accept-Language: es-es
Content-Length: 0
Accept-Encoding: gzip, deflate

1. Probably your device doesn't report location for some reason.
2. It can indicate a network issue.

Hi Anton, regarding question 1: in places where mobile coverage is poor, the client (apparently) can not send positional data. Would it be possible to add functionality that would store the measured positions in memory and send them in a batch once the smartphone has a good mobile signal?

Traccar Client already does that.

interesting. Today a cross-country trail groomer sent these positional data:

https://nabezky.sk/node/112259

I thought the missing segments were caused by (objectively) poor mobile signal. Assuming the groomer driver did not move his smartphone during the drive and the satellite visibility was comparable on segments where data are missing to adjacent segments where they are present (that should be the case), what could be the problem with recordings of today's trip? I guess I could take a look at the device log to check whether the data is missing due to poor GPS signal. Is it possible to access/share (say - via email) the app log?

Sure, but how would you get logs for that period.

that's what I am asking :-) Is it possible to export the log from the app?

By the way, the driver told me that in places where "points" are missing on the map the signal is poor.