Logs in wrong order after using Drafts

[+beinhart]

Yesterday I was caching with the Android App. The web site shows me the logs in this order:

NM1 https://www.geocaching.com/seek/log.aspx?LUID=8d03fc27-3697-44a2-b6ab-4a38f97cbf8e

F1 https://www.geocaching.com/seek/log.aspx?LUID=90bb0632-e36d-4a66-a8aa-c4a6c2c01b35

F2 https://www.geocaching.com/seek/log.aspx?LUID=ab93e636-b772-437c-a452-0b5a5f8ac65c

F3 https://www.geocaching.com/seek/log.aspx?LUID=e420dd4f-d33a-4679-afc9-40a9b5d84217

F4 https://www.geocaching.com/seek/log.aspx?LUID=56c42508-1628-4c3f-8a14-8b1ef2670b42

F5 https://www.geocaching.com/seek/log.aspx?LUID=9defa1d4-41f8-43e9-97a5-e39502540e1d

F6 https://www.geocaching.com/seek/log.aspx?LUID=d1527418-2f9d-419b-b3ef-29ba3e5ca8fe

F7 https://www.geocaching.com/seek/log.aspx?LUID=b148b13a-a6b8-433f-b2d2-dc8f09a28afd

F8 https://www.geocaching.com/seek/log.aspx?LUID=986b9b6b-f5d0-47c3-9f0f-297f2d285d67

F9 https://www.geocaching.com/seek/log.aspx?LUID=25ff94db-4d92-4cb2-9441-b31f54785bd8

F10 https://www.geocaching.com/seek/log.aspx?LUID=bfd2d7ee-9a86-4cc3-a224-b3e0e0fc3a6f

F11 https://www.geocaching.com/seek/log.aspx?LUID=3b887a2e-44a9-4fe0-8a8f-4ecca0d8422d

F12 https://www.geocaching.com/seek/log.aspx?LUID=67969c95-6ec6-4a8a-a6d5-40cf3e3058d2

F13 https://www.geocaching.com/seek/log.aspx?LUID=4d420b31-7c3f-4a2f-aec5-6bc714432d21

 

But this is not the order in which I found them.

I first found F13 (order is correct) at about 10 a.m..

Later I found F3 (maybe 12 a.m. or 1 p.m.), then F2, then F1.

The next cache was F13. But as this is a challenge and I wanted to add the project-gcc checker output to my log I did not log from the App anymore but just wrote draft logs. The order of the logs was F12, F11, NM1, F10, F9, F8, F7, F6, F5 and F4. Later in the evening on my PC directly on the web site I went through all the drafts and logged them in the order I found the caches.

 

The order for the logs that I logged in the App (F13, F3, F2, F1) is correct.

NM logs are not necessarily in the right order, but I don't care.

The logs from F12 up to F4 are in the right order. But they are not above the logs from the App, they are inserted somewhere in between. How can that be? I rely on the correct found order for some of the statistics.

Side note: in my holidays in the last weeks I also logged some caches directly and for others I first wrote a draft. When I later published the draft (using the App) the logs still were in the correct find order, the drafts were inserted at the right place and not appended to my find log list.

 

If it's relevant: I am in Germany/Berlin time zone.

 

Regards

Werner

Edited July 9, 2018 by beinhart

[+on4bam]

Times and GS has always been a bad combination. If you want all logs to be in the correct order you should use the same method for all logs. Mixing ways to log is a proven way for disaster.

 

[+noncentric]

I had a similar issue.  HERE

 

Solution:  Delete your logs for the day and resubmit them all, using the same method.  Either from the website or the app.

 

Lesson learned:  Submit all logs for a specific day using the same method.  It's not about how the Drafts are created, but how the final logs are submitted.  I think that when final logs, either live or from drafts, are submitted via the app then the timestamp of that log is changed from the actual time it is submitted - but when final logs are submitted via the website, then the timestamp of that log is just the actual time it's submitted.  Just a guess though, as I haven't fully tested this.

[+beinhart]

On 20. July I was out on a tour again, this time I only logged directly from the App. Two caches had been disabled, so I needed to log them on the geocaching.com web site.

Again the logs are out of order. The caches logged from the App are in order. But the caches logged on the web site are out of order. One cache I logged in the afternoon is listed as the (early) third log on this day. Log number 13 and 14 (found and NM for same cache) are listed as logs number 5 and 6. So web site logs seem to be logged with -n hours offset compared to App logs.

 

This is a crap and renders logging with the App useless.

 

Can someone from Groundspeak please comment!?

 

Regards

Werner

Edited August 12, 2018 by beinhart

[+noncentric]

1 hour ago, beinhart said:

On 20. July I was out on a tour again, this time I only logged directly from the App. Two caches had been disabled, so I needed to log them on the geocaching.com web site.

Again the logs are out of order. The caches logged from the App are in order. But the caches logged on the web site are out of order. One cache I logged in the afternoon is listed as the (early) third log on this day. Log number 13 and 14 (found and NM for same cache) are listed as logs number 5 and 6. So web site logs seem to be logged with -n hours offset compared to App logs.

What I've found is that logging via the website, either on computer or phone browser, attaches a timestamp that matches when the "submit log" button for that log entry was pressed.

When logging via the app, the app converts the time and so the app log entries end up with an earlier timestamp than when the "post" button was pressed.  This seems to be why some FTF logs show up before the Published logs, with cachers submitting their FTF logs in the field via the app.

 

Now, my experiences have been in the PST time zone and so the time differences that I see might be different from what you are seeing. But the basic answer is that you'll need to submit all logs for a day with the same method, even if they're Draft logs, to have the log entries for that day kept in order. That is the same response I received from Groundspeak when I submitted a Help Center ticket about mis-ordered log finds when I logged some from web and some from app.  My logs were submitted from the Drafts page, but it seems the same applies as if submitting logs live.

 

Note - You can still view and log Disabled caches via the app, but you'd have to Search for the disabled cache in the app using the GC Code.