Ben H

Thanks to both of you for confirming the fix. And sorry for the inconvenience while the bug was out.

I'm glad that your issue seems to have resolved itself. Please let us know if you're experiencing it again. Frustration from non-responsive taps is certainly not the experience we're expecting people to have. This sounds like a temporary hiccup in our search indexing. As new caches are published, those caches need to be indexed in order to be searchable, which is of course required for them to be accessible in the app. During peak times there is a chance that the lag between publication and search availability could be slightly higher, but we're constantly working to minimize that gap. How often has this occurred for you? How long after receiving the email have you encountered the problem? Any additional info might help us. Thanks!

Are you seeing that behavior after the update? If so, it's a bug we'll need to fix. Obviously we know that you need to be able to open disabled caches in order to submit an enable log for them.

We released an update today that should fix this issue. Please let us know if you continue to experience the bug after the update.

Yes Just curious, will this include the ability to search for disabled or archived caches (including ones you don't own)? Currently, if you search by the GC code of a disabled/archived cache, you get the message "Invalid code". Yes, non-owners will be able to search by GC code for and view disabled caches. Disabled caches will also be viewable if they're already in a list/PQ/etc opened in the app. Like the classic app, disabled caches (other than owned disabled caches) will not show on the main geocache map in the app.

This is coming up in the next release. Cheers! Will the app then display ones own disabled caches on the map? Yes

For me (using an API partner app, not Groundspeak's app), I like having the other caches displayed partially transparent. Part of it is awareness of context: I can see what other caches are in the area that I'll be visiting, so I can consider other caches I might want to search for after/instead of this one. Part of it is a reminder that the app is still trying to navigate to a specific cache, and not showing me all the caches I'm interested in. If I see only one cache on the map, it isn't clear whether there are no other caches of interest in the area depicted, or whether the app is showing me only one cache because that's the cache it's navigating to. With the other caches displayed partially transparent, I know that they're there, but that the app is navigating to another cache. This is a puzzling question. I can't speak for cachenscary, but the most important reason I like to see all the caches is that I sometimes pick the wrong next cache. If my GPSr didn't show all caches, I wouldn't see that I'm walking by another cache. That's not the only reason. As cachenscary put it, I'm "always trying to stay aware of nearby caches in real time", both found and unfound caches. Thanks for the responses with additional details. I'm not sure exactly why the question is puzzling, but one of the worst mistakes I/we could make is not to understand why players want a certain feature. I could assume that you might want it for the same reasons I might want it, but those assumptions quite often prove incorrect. Hence the need to ask for additional detail.

Hi there. Yes, you can download generated PQs in the new app during the same 7 day window of time you'd be able to download them to other API partners. You'll find them available for downloading offline in the Lists section of the app. To download one offline, tap the (...) menu to the right of the generated PQ and select Download Offline Data. This is indeed a bug. Can you explain why it's important to you to see all caches when you're navigating to one? Hi Ben, I'm using Android and v 5.02 of the app Thanks! I'll pass your detailed info along to our QA team for investigation.

Thanks for reporting the issue. Can you let us know which operating system version and app version you're using?

Thanks for the continued reports on this, everyone, and thanks for your patience. We have submitted an update to Apple with the fix for this bug and we're waiting for their approval. We hope it is approved soon so that we can release it next week.

Thanks for the detailed report! That level of precision in explaining your problem is very helpful. Fortunately, this is a bug we're already aware of and we already have a fix completed. We have submitted an update to Apple and are waiting for their approval. We hope it is approved soon so that we can release it next week.

Thanks for the additional info. I'll pass it along for further investigation.

Sounds like you may have multiple issues going on: 1) We made a fix in our 5.0 Android release that limited the TB inventory in the app to inventory only, no collection. Have you downloaded the latest version (now 5.0.2)? Please try that and let us know whether you continue to see trackables in your collection showing in your app inventory. 2) Thanks for the info on the syncing issue. We'll investigate. In the meantime, any additional info you can provide would be helpful for us to trace the problem (more detailed repro steps, your OS and app versions, links to the TB logs in question, etc). Thanks!

Caches on your ignore list are now filtered out from search results. If you want to open a cache you've ignored, you can still find it with a search by GC code.

Caches on your ignore list are now filtered out from search results. If you want to open a cache you've ignored, you can still find it with a search by GC code. Thanks for the constructive feedback. We're currently working on our 5.1 release which will include a few small, non-drafts improvements and should be available next week. After that, our 5.2 release will focus on further improvements to drafts, including addressing both of your requests above. The time zone issues are indeed tricky, but we've got a new approach in the works.

For anyone still watching this thread, we added Drafts functionality in our latest release last week. More info in the release notes and on the blog: http://forums.Groundspeak.com/GC/index.php?showtopic=343337 https://www.geocaching.com/blog/2017/03/3-reasons-to-write-great-logs/

Thanks for reporting the problem, all. We're working to fix the bug ASAP.

Thanks for reporting your issue. A few others users reported similar problems, so we're investigating.

We're working to implement this soon.

Thanks for reporting the problem. This is a bug which we'll fix ASAP. The draft toggle's position is "sticky" across multiple logs. If you prefer to write drafts and switch to drafting mode on one log, you should continue to see the toggle in draft position on subsequent logs until you switch it back. Please let us know if that's not happening for you.

Thanks for these reports. We have confirmed the bug as reported. We'll get it fixed ASAP.

Hi there. Thanks for reporting your problem. I'd love to track down the issue if there is one. Can you give me a list of the steps you're going through to reproduce the problem and describe what happens when you go through those steps? Any screen grabs and/or info about your app version and OS version would also be very helpful. Thanks! Thanks for the offer. Samsung Galaxy S5 Android 6.01 Geocaching 4.10 (not classic) I am a current premium member with 16 favorite points available Find cache. Go to "log Geocache" Choose "Found it" Type Text for log Touch Heart Icon, it turns green Save log by touching check mark The app saves the log, marks GC as found, but does not designate the GC as one of my favorites nor does my favorite point totals change. Verified log save and favorite failure on GCing .com upon return to home base computer. I have tried three different times to mark a GC as a favorite at time of find. Same non-result chronicled above. I did go back and favorite one of the failures from the Geocaching web page. However, I have left the last failure as is to prove the point. Last failure = GC12Y8N East of the pass. So far, GC support has been no help. They asked me to reinstall app which I did. I reported back to them that it didn't work, no response from GC support. If you need anything else, let me know. Thanks. SE& Hello again! I just gathered a little more info and learned that we fixed a bug very similar to yours in our latest release (5.0.1). That release is currently trickling out to Android users; you may see it available to you later on today. Once you have the update, can you try again and report back whether your issue is resolved in the new version? Thanks!

Hi there. Thanks for reporting your problem. I'd love to track down the issue if there is one. Can you give me a list of the steps you're going through to reproduce the problem and describe what happens when you go through those steps? Any screen grabs and/or info about your app version and OS version would also be very helpful. Thanks!

For now, you're right: you can not start a draft on geocaching.com. Today's release was primarily about adding drafts to the app. The website changes were more cosmetic to maintain consistency between app and web. We may revisit the tools related to drafts on geocaching.com as we continue to build out the feature in the app.

Hi there. This feature will be available in our next app release. You should see the update later this week.