Nic Hubbard

There are no "developers", it is just me doing development.

Loading archived caches on the map similar to a search isn't possible. The geocaching.com API does not provide a way to do this. The two options you have, are if you know the GC code, you can search for it. Or you can use another service to create a GPX of archived caches and import that GPX.

I was incorrect in my statement. 

Would you be interested in beta testing the fix? If so, please email support@cach.ly

This issue is caused by the removal of the trackable bulk visiting API from the Geocaching HQ API that Cachly uses. I am working on a fix currently and hope to have it released this week.

Thanks, I will give this some thought.

This will be coming in a future release. I have already added it for CarPlay which is in development.

21 minutes ago, aheppis said:

But here I have two tabs - User and Cache.

When I create a user waypoint I have to switch between the two tabs all the time.

If the waypoints would all be in one 'tab' I could see them at a glance and it's much easier to compare waypoints.

L4C had own waypoints and cache waypoints below among each other on one screen.

Can you explain your use case of when it might be helpful to have both on the same screen?

23 minutes ago, aheppis said:

I am using offline lists including caches which are far away from each other.

Sometimes when I am near one of that caches I'm checking for other caches around that cache. But then I want to see only caches which I haven't found before. Then it would be great when I could open the position of the cache from the offline list in the live tab using all filters which are set there. So I could check for unfound caches around quickly without using other offline lists or something like that.

Got it. Would you mind logging a feature request for this on our tracker? https://github.com/cachly/issues-tracker/issues

This will help me since you can add additional information there about your request. Thanks!

Yes, just view the waypoints screen of the cache:

4 minutes ago, aheppis said:

Hm, this makes it quite uncomfortable if I just want to look around for unfound caches.

Maybe you could add another button to open the coordinates of the cache in the live tab!?

Can you explain this a bit more?

Can you please send me a crash log? https://help.cachly.com/article/115-how-can-i-send-a-crash-log

Red dashed lines are just general paths/trails. Brown dashed lines are are tracks, which are often lesser roads that are gravel or dirt. Yellow and black would correspond to the actual trail system, they should have signage for that when on the trails to tell you what it means. 

Yes, look in Settings and there is an option to show waypoints. Turn on full cache data and the "Show all Waypoints" option.

This option does not use filtering, but you could add them to another offline list and do the filtering there.

This is a feature I have planned for 8.1.x.

I just have not had time to rebuild these for the whole world. I do not have an ETA on this.

Yes, view the cache then tap the ... and choose the "Find Caches Near This" option.

Yes, HQ did reach out to developers and have asked that we remove the "Visit All" option. This does not have anything to do with TB auto-visits, so that won't be affected.

As far as I know, the official geocaching.com does not allow GPX importing. What is your use case?

That were an update to iOS that broke this, and I need to rebuild it. Hoping to get it fixed soon.

That is pretty massive. I would delete the caches in smaller groups using the "Delete visible caches" option when viewing a small subset of caches. 

I would recommend in the future to create multiple lists that are smaller.

Thanks for reporting this. I created a report in my issues tracker, please add any additional details: https://github.com/cachly/issues-tracker/issues/5300

CarPlay development happens almost daily. The issue is, there are MANY differences to iOS and limitations as well as features that take a lot more time to develop within the CarPlay constrains. Because of this is it difficult to say when it will be released, but I am getting close.

Not with a single action, but you can create text templates and setup log defaults that would make creating your log much quicker.

This issue has been fixed.

I have no additional update on this, other than that HQ is looking into the issue. 

There have been many API bugs over the years and they get fixed relatively quick. Sadly this would be affecting all Cachly users.

Please take a look out the Cachly user group which is where most of the discussion about things like this takes place: https://www.facebook.com/groups/CachlyUserGroup