AnyMules

As another new Cachly user, coming from long term GeoSphere usage, there's a few things I used to use all the time in GeoSphere that I'm missing in Cachly, especially with Offline caches.
With GeoSphere, I was able to import my whole GSAK database (40,000+ caches) in to the app, and while it wouldn't show them all at once (limit was 8000), I was able to use filters on the offline lists to display subsets of caches (ie, just Unknowns, just those with Corrected Coordinates, just T5 caches, only caches within X distance, etc).  I can't seem to see any way of:
- having this many caches in Cachly without it crashing when accessing a large list
- filtering a list to show a certain subset of caches
- hiding my Found caches if they're present in my list
- the "List" of offline caches doesn't seem to reflect in any way my current distance from the caches
If any of the above can be done already and I'm just missing something, then I'd be grateful to learn how.
Thanks for otherwise what appears so far (only 1 day's usage, with some swapping back and forth to the old app) a great app!

Done! I fixed this in a few other places as well.
Once place I didn't change it is where we use Google Translate. In this case I think it works well to not have to open Safari.

Hey @Nic Hubbard,
I spent most of the afternoon today out caching and made about 25 logs with Cachly. All logs look good date wise, so I'm pretty happy with that. I only had to refer back to "the other app" on a couple of occasions where I had corrected coordinates stored, but hadn't migrated them to Cachly (or geocaching.com) yet.
So I'm pretty happy with the way this app is now working with regards to the dates. It all looks correct (although I'll probably need to test one day around the midnight cutover, but that won't be for a while yet). 
Thanks again for all your work on this issue!  

Hi @Nic Hubbard
I tested it this morning and it seemed to work fine. I created a cache note for a cache at 6:00am my time which would have previously shown incorrectly and it appeared on the correct date on geocaching.com. So far so good. I'll do some more logging with Cachly at various times over the weekend and see how it goes. Thanks for all the work you've put in to this. 

I have fixed this issue, with help from Clyde from GSAK.
I will push out a new beta with this fix and Settings option. It will be in 2.0.2 so we will have to wait for Apple to approve the beta, which is pretty quick.

Thanks @Nic Hubbard.  I'll eagerly await this change, and use one of the workarounds in the mean time - probably "find cache using Cachly then log it with Geosphere", as that has worked for me the last few days, although it does mean that I need to keep two copies of the caches on my phone up to date - but that's not too difficult to achieve with a daily export of caches from GSAK via dropbox in to each app.
Again many thanks for your rapid responses and eagerness to make your app more functional and the best caching app out there.  I'm loving many of the features of Cachly.

Yes, I think adding an option with a big warning about this is what we will do. Still working on the specifics, so it might not be for a little while until we release that version. 
Thanks for everyone's input.

Thanks again @Nic Hubbard.  Your assistance and quick response on these forums (and emails) is greatly appreciated.  
I've had a friend who uses c:Geo on Android to put a Write Note on that cache as well, and that's showing "Today" - so it appears that either a) It is Today now, or b): c:Geo is also doing whatever is required to log the correct date too.

Thanks @Nic Hubbard.  Let me know when you're done with all the Test logs on GC69QD2 so I can delete them.

With the option to navigate to a cache with TomTom, the TomTom app launches fine and "show"s a marker for the cache location (which I'm assuming you're using a "tomtomhome:geo:action=show&lat=[LATITUDE]&long=[LONGITUDE]"), but then additional screen presses are then required to set that as the location and start navigation.
Is it possible to have it changed to "navigate" to the cache (or the waypoint that is selected) using "tomtomhome:geo:action=navigateto&lat=[LATITUDE]&long=[LONGITUDE]&name=[WAYPOINT]" instead so it works similar to the Google Maps and Apple Maps options?

Thanks @Team DEMP, I can understand that there are people who may want it to stay the same, and I would be happy for an option for people to switch the behaviour on and off if that's deemed a suitable alternative by @Nic Hubbard.
Logging caches on the web site also logs them with what I consider the "wrong" date as well - as, again, it logs the find with whatever the date and time are at GC HQ.  For those of us "down under", this is quite often the "previous day" until late afternoon when the US catches up to the right day.
So, unless something can be added to the app to make it use the local date/time when logging a cache, it will always be logging them at the GC HQ date/time which completely throws any stats generated out, and also can screw up cache streaks as, while I may have found a cache "yesterday" and "today" my time, the "HQ time" may show them both being on the same day due to the time difference - this means going back on-line on the web site and manually editing cache logs to get them to be logged on the correct day.  This was particularly painful the other day when I was using Cachly offline in a non-phone reception area all day and had to go back and edit 60+ cache logs individually to correct them all.
The Geosphere app appears to have some fix for this, and logs things at the local date/time it is told to.  GSAK also seems to use the dates it is set to use as well from what I have seen.  If I can just use one app to log everything correctly, then that'll make life much easier.  I'm keen to try the "fixed" version in the beta @Nic Hubbard sent me tomorrow to see how it fares.

Glad to hear it's on the list. Thanks for the quick response as usual.