Lost finds
-
Desert_Dust-AKA-D_D
- Posts: 9
- Joined: September 23rd, 2013, 3:10 pm
Lost finds
On 05/22 I made 97 finds on two groups of caches. All the finds in one group popped up on here right away, but the other is yet to post here. I have even tries asking for an update a couple of times but nothing. Any idea what's going on? Rechecked on geocaching.com and the finds are there.
- Corfman Clan
- Global Moderator
- Posts: 914
- Joined: January 17th, 2012, 12:21 am
Re: Lost finds
I took a look at this and don't see what the problem might be. It appears that only 29 of your finds are shown. I went through the site logs and can see when you logged in but for some reason no caches are being updated. Would you mind if I use your account on my test box so I can trace what is happening? I won't need any passwords, just your account token that is already being stored on LonelyCache.Desert_Dust-AKA-D_D wrote:On 05/22 I made 97 finds on two groups of caches. All the finds in one group popped up on here right away, but the other is yet to post here. I have even tries asking for an update a couple of times but nothing. Any idea what's going on? Rechecked on geocaching.com and the finds are there.
-
Desert_Dust-AKA-D_D
- Posts: 9
- Joined: September 23rd, 2013, 3:10 pm
Re: Lost finds
No problem. Would like to get this resolved before I log anymore finds.
-
Desert_Dust-AKA-D_D
- Posts: 9
- Joined: September 23rd, 2013, 3:10 pm
Re: Lost finds
I had a thought earlier. I want pretend I totally understand how LonelyCache functions. Actually thought it only updated early in the morning, but I see caches I have just logged pop up in it right away. But my thought was this, after logging my finds on geocaching.com I had started deleting them off my GPSr. In the process I realized I had logged one cache twice, so immediately went in and deleted the second entry. Any chance that if lonelycache was doing it's thing and in deleting that entry I may have caused it to corrupt the data? Just something that popped into my head.
-
Desert_Dust-AKA-D_D
- Posts: 9
- Joined: September 23rd, 2013, 3:10 pm
Re: Lost finds
I picked up one find today and logged it. It popped right up on LC. Then deleted my first find from 05/22 which had not posted on LC. Then logged it again and it popped right up. Deleting the finds and then logging them again maybe the only way we'll get this resolved but I will do nothing more till I hear from you.
- Corfman Clan
- Global Moderator
- Posts: 914
- Joined: January 17th, 2012, 12:21 am
Re: Lost finds
After using your account and stepping through the debugger the only thing I can say is that it appears there is a problem with the Geocaching.com Live API. What LonelyCache does is request all your found logs and Webcam Photo Taken logs for the past week, requesting 30 logs per page. If there are more than 30 logs, then the API should return the first 30 logs. LonelyCache would then request the next page of 30 logs, etc. If less than 30 logs are returned, then LonelyCache figures that all the logs for the requested time frame have been returned and is done. The problem is that the API is returning less than 30 logs. So as far as I can tell, LonelyCache is behaving as expected, but the Geocaching.com Live API is not.
I'll have to report this problem to Groundspeak so they can fix it. In the meantime, your finds should show up in LonelyCache within a week from when you log them.
I'll have to report this problem to Groundspeak so they can fix it. In the meantime, your finds should show up in LonelyCache within a week from when you log them.
-
Desert_Dust-AKA-D_D
- Posts: 9
- Joined: September 23rd, 2013, 3:10 pm
Re: Lost finds
Thanks for all your time and hard work on this issue. As of this morning 24 more from 05/22 have been credited. Thanks again
- Corfman Clan
- Global Moderator
- Posts: 914
- Joined: January 17th, 2012, 12:21 am
Re: Lost finds
I received confirmation from Groundspeak today that they have logged this as a bug. There was no mention of when resolution may occur but I wouldn't have expected that anyway.
From what I saw analyzing this, I believe the problem has something to do with a user deleting one of his/her logs but I have no way to verify that but the above story line does corroborate it. Groundspeak is aware of my supposition.
From what I saw analyzing this, I believe the problem has something to do with a user deleting one of his/her logs but I have no way to verify that but the above story line does corroborate it. Groundspeak is aware of my supposition.