Ben H

We released a fix around mid-day today that should have resolved this issue. Please report back here with continued problems downloading lists offline.

We released a fix around mid-day today that should have resolved this issue. Please report back here with continued problems downloading lists offline.

Thanks for reporting this issue. We are actively working to resolve it and hope to deploy a fix shortly.

Thanks for reporting this issue. We are actively working to resolve it and hope to deploy a fix shortly.

Thanks for reporting this issue. We are actively working to resolve it and hope to deploy a fix shortly.

Hi Keith. You said that you're using an iPhone, but your screen shot looks like the Android app. Can you confirm which platform you're using? If it is iPhone, the same bug I previously mentioned about driving directions applies to the compass. We're still investigating a fix for that. In the meantime, the compass for a cache with corrected coords will accurately show distance to the corrected coords if you tap the compass after you've tapped Start to enter navigation mode.

Thanks for reporting your problem. Are you using the Android app or the iPhone app? If it's the Android app, it's a new problem that we'll need to investigate. If it's the iPhone app, we're already aware of and working on fixing a bug regarding driving directions to solved coords. On the iPhone app the driving directions currently will route you to the posted coords if you start driving directions before navigation in the app (hitting Start), but will route you to the solved coords if you start driving directions after navigation in the app. So in the short term there is a workaround and we're working to fix the bug.

The updates mentioned in the release notes are now available to all players. If you’re still not seeing them make sure you’ve updated to the latest version and/or try relaunching the app.

Are you using the 6.0.0 Android update? If so, can you please update again to 6.0.1. We released that yesterday to fix the main crashing issue that we were seeing on the prior version.

If you are using c:geo, please see this answer from them.

You’ve discovered a glitch in the matrix! Honestly, though, we had a hiccup in our planning for releasing the changes mentioned in the release notes. Sorry for the confusion. We’ll start rolling the changes out next week and if all goes well everyone should have access by the end of the week. Consider this a teaser.

Glad it worked for you!

Your problem may be caused by iOS replacing your straight apostrophe with an angled one. This is due to a new feature in iOS 11 called Smart Punctuation. (See more here: https://www.jordanmerrick.com/posts/ios-11-smart-punctuation.) If you're not careful, you may be inadvertently using a smart quote instead of the straight quote that's actually in your username. The smart quote is now the default on the iOS 11 keyboard. To get around the iOS 11 change, you need to long press the single quote character and manually select the straight apostrophe character. Alternatively, you can disable the smart punctuation feature as described in that link above. Please respond back here of that does not resolve your issue.

Glad to hear that fixed the problem for you. We're also working on an additional fix to reduce situations like this where you need to do a hard refresh.

Thanks for reporting your problem. Can you please try a hard refresh to see if that resolves the issue?

Thanks for the reports on this issue, everyone. We have, indeed, been working on fixes over the past week. Our most recent changes were released this morning and our internal tracking indicates that today's updates resolved the errors that were happening. Please do try using the Garmin Express functionality again and let us know here or through the contact form on https://www.geocaching.com/help/ if you continue to experience problems.

When you are viewing your list of caches in list form (as opposed to a mapped list), you can pull down on the screen to refresh the contents of the list.

Thanks for letting us know.

Thanks for confirming. Fortunately, our analytics show that the crash is not affecting too many users right now. It happens during database migration after the update and is probably more likely to happen if you have many drafts, personal cache notes, or caches saved offline. Unfortunately, if you are affected by this crash after updating the only remedy right now is to delete the app and reinstall it as you did. We know that is not acceptable as a "solution", though, so we're working right now on a fix for the migration crash. Thanks for your patience.

I'm sorry you're both having trouble with this release. We're aware of crashing issues for some users and working to resolve them ASAP. dj1974 - Can you confirm that you're update to the 5.8.5 version?

The 5.8.5 app update which fixes this crash is now available in the app store. Please update to that version and let us know here if you continue to experience the same problem.

We're very sorry the update has caused crashes for you. We're aware of the problem and we're working on a fix right now. We're trying to push out another update today or tomorrow to fix the issue. Thanks for your patience!

Thanks for the feedback. We absolutely do intend to update the OSM maps with new data regularly, but unfortunately it has proven elusive to implement updates in a way that works well with our map tile server solution. We do understand that players are anxious to see updated OSM data on geocaching.com and in the app and we're sorry that it's taking far longer than we expected to provide that updated data.

This bug fix narrowly missed making it into the 5.8.2 release, but it will be in the next one.

Thanks for the reports on this issue, everyone. We've been trying to reproduce the compass problems described and so far we haven't been able to. We have confirmed that if the iPhone compass calibration app does not have location permissions then the compass in the Geocaching app will not function correctly. To find out if that could be affecting you, please make sure the "Compass Calibration" switch turned on (see attached image). Also, please note that this is not the same as giving the standalone "Compass" app location permission. If anyone tries this, we'd appreciate a report back here as to whether or not the Geocaching app issue is resolved for you.