Nic Hubbard

Yes, it looks like this is affecting offine maps. Working on a fix.

Thanks, will work to regenerate this map.

We don't have an updated page at the moment. Do you have a screenshot of what you are wondering about?

Please see our help article about this: https://help.cachly.com/article/34-why-dont-i-see-all-of-my-geocaching-com-friends-in-cachly

I have considered some options like this, but currently the focus is to use the watch complications as a launcher for the watch app.

Can you send an email to support@cach.ly with the GPX file so that I can look it over? Thank you!

Thanks for the suggestion!

Hmm, that is strange!

In your specific case, I am not sure. Offline maps are the only thing that would take up that amount of space. The last resport is to delete Cachly and install again, making sure to backup your offline lists.

iOS might not updated the usaged without a restart. I would restart your phone then check again.

What does your Usage screen show? Cachly should never take up that much space without offline maps. Maps are the #1 source of large data sizes in Cachly.

No, there are 1000 other important things that are priority before this.

Are you meaning in Pending Logs, you are wanting a way to bulk insert log text into all of the pending logs?

Only one file per .zip is supported. You will need to import the GPX files one at a time, or have one GPX compressed in the .zip.

It is a server side bug. So a change that Geocaching HQ made to their API (not sure what) is now triggering the 500 error when full cache data and 100 caches are requested.

Do you have the "Full Cache Data" option turned on? If so, try turning that off and see if that helps. If it DID fix the issue, can you let me know what you have for the number of caches to load setting? Is it 100?

Also, if you turn of live filters, does that solve the issue? If it does, Please make sure to see my above comment about sending debug data, it would really help.

Hmm, have you tried turning off all filters to see if that helped? Also, can you try the searcha again, then use the option in Cachly to contact support and send us an email. Then make sure to include debug data so we can see the request that is being made.

Simple answer is yes, but it would cause some irregularies with how many caches are returned. Would have to educate the user before adding a filter like this.

Thanks for the suggestion. The geocaching.com API doesn't currently support this, so we aren't able to add this feature currently.

Hmm, that is really strange. You should never have to delete Cachly. A 500 error comes from the geocaching.com API.

Thanks for the suggestion, we are looking into this.

Thanks. I am still considering this for a future version.

Hmm, something might have went wrong with the iOS migration process. In this case I would delete Cachly and reinstall as you will want to start fresh on a new iPad.

The geocaching.com API does not support sorting this way so it isn't something that we an add.