FTF! But…

On Sunday I was lounging around in bed without a care in the world when I noticed an email notification for a newly published cache. There were several actually, but this one caught my eye because it was just over a mile away from home. I’m not exactly an FTF hound, but when one shows up this close to home, I’ll get out of bed for it on a lazy Sunday morning. I raced over to it and started looking. Eventually, I managed to find a fake rock and made the claim. Along with the lovely location pictured above, it was a great cache for the day.

The “But…”, however, is the problem I encountered in the search. When I first looked up the cache, it didn’t load all the information, but I just assumed that maybe the wifi around the house was wonky for a bit. Once I got to the GZ, my real problem occurred. When the cache was posted, it didn’t entirely populate. It didn’t show up on the map for either of the apps I was using, Groundspeak’s Geocaching app and Cachly (the latter has a ton of useful options and settings, the former provides slightly better navigation I think). Waypoints, descriptions, hint… Nothing. Other than D/T and size, that is. This isn’t the first time I’ve seen this and I’ve heard others report it, too. Sometimes new caches show up in browser but not on mobile. Don’t know why that is, but that may be something Groundspeak should work on. It’s not like mobile represents an insignificant part of the user base or something like that. That first hour or so might be important to some people or something. Jes’ sayin’…