Nic Hubbard

Yes, this is a known issue that will be fixed in our upcoming 2.0 release. Sorry about that!

I should have updated this before, but this has been fixed in our most current beta and will be in our 2.0 public release.

Steve, can you give me a bit more information about the crashing? What screen did it crash on? How long did it take to crash Could you reproduce it every time Thanks!

I can't say for sure when it will be released, as that has not been finalized. We are just working to make sure it is our best release yet.

Moving around the map and refreshing is quite simple (in a future version we will have a live map). You can also tap the gear icon in the search bar to bring up search options to greatly refine your search. You can also search for locations by address, GC code, coords, etc. Lists are a way to group/save caches. In our upcoming 2.0 version you will be able to refresh an entire list. Hope this helps.

Loading all caches isn't possible as the API we use from geocaching.com only loads 50 at a time. You can then save those caches to an offline list if you want to save them.

After you load the first 50 caches, do you see three dots inside of the refresh arrow? It should be allowing you to load more and more caches in your area. Can you try moving the map elsewhere and refreshing? What do you mean? Is this a list that you created in Cachly or geocaching.com?

Yes, version 2.0 is upcoming and it packed with new features including offline open street vector maps. We will be doing a blog post soon that outlines all of the upcoming 2.0 features. If you are interested in beta testing or helping with translation, just contact us through the support option in Cachly. The update will be free.

We have this on our list to add, but so far it doesn't seem that Tom Tom has a way for us to integrate with their app. There isn't currently a way to send it coordinates.

I agree. I am going to be rebuilding the PQ section to integrate it into Lists. There shouldn't be a connection. In the next beta PQs will download directly into Lists, and you will be able to save the PQs into an already created list.

This is on our feature list as well, but likely won't make it into 2.0 as it isn't one of the high priority features.

Great idea. Will add this to the feature list and add to 2.0.

Can I assume you meant logging two Pending Logs?

Good find! Will get this added to our bug list.

Glad it worked! Thanks to Groundspeak for fixing this issue!

Sorry. So many support emails and beta testers can get me confused.

Just contact support using the app and ask to be a beta tester. Thanks!

I am very well aware of this issue, and it is something that I have wanted to correct for some time. It seems like it should be a fairly straight forward thing to fix, you would just need to get the users current time zone and then add the difference in hours to PST. However, I am not convinced it is that easy. After 2.0 is release we will make sure to look into this issue deeper and if you are willing we would love for you to test it.

We have looked into iPad support, but currently our focus is on iPhone as that is what the majority of our users use. But, we still have it on our feature list.

We do have this feature on our list to add someday. Just not sure when, hope we can add it soon.

But on startup Cachly doesn't load Offline PQ automatically. So that can't be the issue. I think I have found what is going on and will have my beta testers try it later today.

Sorry Bernie, for some reason I was never alerted about this reply. No, this wouldn't be possible because Groundspeak owns the the coord.info domain, and without being the owner we cannot open those links in Cachly.

Users should be first! We have not started work on this feature yet as our we are working on many other features in 2.0. Hopefully we could add it soon.

When you had issues, it was during startup? I want to make sure to try to get to the bottom of this, even if it isn't happening anymore.

Groundspeak was gracious enough to work on this issue and it should now be fixed. I just tested it on a cache that wasn't mine and it worked. Let me know if you guys have success.