Cymbios Posted March 28, 2012 Share Posted March 28, 2012 Just started geocaching at the weekend, and I'm completely hooked! Great fun I have been logging my finds on the official geocache app on iPhone. My latest find was today: http://www.geocaching.com/seek/cache_details.aspx?guid=f2d6e0fe-3666-489c-8b0c-abc11ec159ed On my iPhone it shows that it was logged today (28th March), but on the geocahing website it shows 27th. Hmmm. Anyone got any ideas as to why? first I thought I had the wrong time zone in my profile settings, but that seems fine. Quote Link to comment
+Kochibu Posted March 28, 2012 Share Posted March 28, 2012 I believe it is the website's internal settings. My first Geocache for example, is listed as published on January 20th when infact it was already the 21st in Germany. If it ain't the same date yet, change it manually. Quote Link to comment
+TheKingaroos Posted March 28, 2012 Share Posted March 28, 2012 (edited) Similar happened to me yesterday too. I logged two finds but it showed a day three days earlier (i.e. I logged them on 27th March and they're showing 24th March). The one I logged today is correct though. I wonder if it was anything to do with yesterdays website update. I didn't realise I could change the date so I've corrected it now. Edited March 28, 2012 by TheKingaroos Quote Link to comment
Cymbios Posted March 28, 2012 Author Share Posted March 28, 2012 Ok, that makes sense. Just a little bit irritating having to change things on the website after logging on my iPhone. Anyway, on with the caching! Thanks for your reply... Quote Link to comment
+NicknPapa Posted March 28, 2012 Share Posted March 28, 2012 Another thing that happens, if you log multiple day's finds and change the date for the first you have to change it back when you start on today's finds. Quote Link to comment
+The A-Team Posted March 28, 2012 Share Posted March 28, 2012 Similar happened to me yesterday too. I logged two finds but it showed a day three days earlier (i.e. I logged them on 27th March and they're showing 24th March). That's actually a different problem. Something changed a few months ago with respect to how the default date is determined when logging through the website, which is what you ran into. On the other hand, the first 2 posters have experienced the disconnect between the time zones used on the app and the website. See Moun10Bike's explanation here: This comes up a lot and is not actually due to a bug in the app but rather in inconsistencies in the database that have built up over time (no pun intended). The gist of the issue that when logging a cache via the web site, the time stamp is (and always has been) set to noon Seattle time on the selected day. Conversely, logs posted via the API use UTC. The break occurs when the site then reads these differing time stamps. We have a lot of work to do to overcome this issue. Fixing it is a high priority but very complicated for a variety of reasons. Quote Link to comment
+GrateBear Posted March 29, 2012 Share Posted March 29, 2012 I find that on my work computer, the log date that is initially shown is still the last date I logged a find on that computer. Not a problem with my home PC of Mac. I think it has something to do with the entire system at work, as the maps don't show on the cache page. Quote Link to comment
+Hingis20 Posted July 17, 2015 Share Posted July 17, 2015 This has been happening with me lately. For example I found a cache today(July 17th) and logged it and it showed up as July 15th. So I went in and changed the date but it still hasn't been reflected on my stats page as finding a cache for today. Can it takes a few hours to update or? Thanks Quote Link to comment
+jellis Posted July 18, 2015 Share Posted July 18, 2015 Did you log it with your smartphone? If you did sorry I can't help you other then to say go on a computer or your phone's browser and change it. If you logged it on a computer most likely it remembered the date of the last entry you made just before it. Like if I cached a bunch of days and only just got around logging them then, lets say logged a cache on the 15th, and then you wanted to log one you did on the 17th you have to physically change the date because it remembers you logged the last cache on the 15th so it thinks you are still logging that day. Sometimes it's a good thing and sometimes not. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.