ari54321

Thank you for reporting this issue. We are currently looking into a fix.

Thank you for reporting this issue. We are aware of the bug and are looking into adding the link back. As you noted, for now players can use the direct link as a workaround (replacing the "BM" code at the end of the URL with the list they want to view feedback for (e.g. for this list with code BM21VBT, players would be pointed here: https://www.geocaching.com/bookmarks/ratings.aspx?code=BM21VBT)

Thank you for reporting this issue. We fixed the bug, and the bulk add option is available again!

Thank you for clarifying this! We are looking into the issue.

Thank you for your report. There are two ways to add multiple caches to a list at once that still working in the new version: When viewing a list, select multiple caches on the list using the checkboxes and select the "Add # to List" button (to add the caches to a different list) When viewing a list, select the "+" button in the top right corner, then "Add bulk GC codes". You can enter bulk GC codes separated by commas to add multiple caches to the list. Do you mean that one of these two ways is broken on your end, or is there another option that is not available?

Thank you for your reports! We have released a fix for this issue; you can now view 500 list items at a time.

Thank you for reporting this. This is an unrelated bug; we are not retiring the old ("seek/nearest") search results as part of this release. The team is looking into a fix.

Thank you @Eric van Graveheart @99celing and @The A-Team for letting us know. Indeed that workaround appears not to work; I have updated my previous post. The team is looking into a fix for this issue. Thank you for your patience!

Thank you for reporting this issue of incorrect gallery dates. It appears this issue only affects images uploaded from the view log page. For now, there is a workaround: if you upload image(s) on the edit log page (open your log, select "Edit log", then drag and drop or select photos to upload), these images will have the correct date (log date, not today's date). If you wish to correct the dates of already-uploaded images, you can delete the images and re-upload them through the edit log page. We are looking into a fix for the image upload dates.

We are aware of the issue with drafts uploaded from a GPS device, but that issue is separate from this release. The team is looking into a fix.

Yes, we removed the "Report a problem" feature. All available log types are now available in the dropdown, including Owner attention requested and Reviewer attention requested. Here's what those options look like on an unfound cache:

Thank you for reporting this issue. The team has fixed the bug. Please try again, and let us know if you continue to experience any errors.

As part of yesterday's Adventure Lab® app release, we released a temporary fix for this bug by removing the "Read more" link. Please make sure your Adventure Lab® app is updated to the latest version (1.9.0) to see the fix. For now, we are showing the full Adventure description, but the team is working to bring back the "Read more" button in a future release.

Thank you for your reports. The team is working on a fix for this issue; we will let you know when it is released.

Our engineers fixed the issue earlier this week, and it appears all reviews are displaying as expected. Please let us know if you continue to experience any issues!

The current 100km limit was intended to allow experimentation with Adventures in areas where there is limited mobile phone connectivity. However, because one of the core aspects of the Adventure Lab platform is that players must physically visit Adventure locations, we plan to reduce the maximum geofence limit to 500 meters in the coming weeks. We are also listening to player and creator feedback as we explore ways to ensure that the Adventure Lab continues to grow sustainably as a location-based game. If you believe that any Adventure violates the Adventure Lab guidelines, please report it in the app using the "Report this Adventure" link (located at the bottom of the Adventure's details screen). We review all reports and take action if necessary.

Our engineers have fixed the issue. It should now be possible to sign in and complete Adventures as usual. Please let us know if you continue to experience any issues!

Thank you for reporting this issue! Unfortunately it appears there is no workaround for this bug at this moment. The team is aware of the situation and is looking into a fix. We apologize for any inconvenience and appreciate your patience as we work to resolve it.

Thank you all for reporting this issue. We have fixed the leaderboard so that new Adventure finds (found after May 1st at 7:30 pm UTC) count towards this month's challenge. The team is currently looking into fixing finds from before this time, but we are unable to promise if or when we might credit these finds to the Leaderboard. We apologize for any inconvenience and thank you for your patience as we work to resolve this issue!

This appears to be an issue specific to your account. Please contact us through the Help Center for further information and assistance with this issue.

When we have granted credits to Premium members in the past, we always specified that "Adventures must be set to Public unless Geocaching HQ has given written permission otherwise." (this is also noted on page 8 of the builder guide). We have updated the language shown in the builder to clarify these expectations. Going forward, we plan to distribute credits that can only be be set to public. Please note that under the current credit distribution system, creators with any private Adventures will not be eligible to receive any additional credits. In order to be entered for selection, creators must set all their Adventures to public. For more details about credit distributions, see this Help Center article.

Our team has identified a fix for this issue. Please try deleting your test Adventure again and let us know if you continue to get an error.

Our team has identified a fix for this issue. Please try deleting your test Adventure again and let us know if you continue to get an error.

Thank you for your report. The team is aware of this issue and is looking into it.

The bug has been fixed in a new release we rolled out last week (app version 1.3.46). If you continue to experience the bug after updating, please uninstall and reinstall the app. Let us know if the issue persists.