AnyMules

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.

The "official app" has always recorded the wrong date/time for me too. Making most of my early finds "found" on the day before I actually found them. That's one of the reasons I switched to Geosphere as my app of choice in my early caching days, but given the lack of support on that app, and the promises of updates since 2013, but nothing forthcoming, I switched to Cachly, but the logs seemed to have been marked the same as the official app, hence my request for a change. Thanks Nic - I've now got the new version. I'll give it a test soon, but will probably have to be tomorrow (my time).

Yes please. As I'm currently in a +10:30 timezone (usually +9:30, but we're in Daylight Savings Time now), the date/time of caches I log with Cachly are way out. The last two days I've been using Cachly to find the caches, but Geosphere to log them (to get the correct logged date/time). Obviously, using the one app to do it all would be preferable.

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

Yes, geocaching.com time zone is set correctly to UTC+9:30 Adelaide. The official app does the same thing, caches are often showing as being logged the previous day. The GeoSphere app (which I'm trying to stop using) logs things with the right date and time stamp, so it must be possible. Perhaps it's some sort of double adjustment by the Cachly app and the API.

Yesterday while I was caching, I was out in a no phone coverage area for a long period of time and using Cachly in offline mode. While in offline mode, using offline lists and offline maps, the app worked great. One thing that it would not allow me to do though was to visit any trackables in the caches I logged as each time I went to the Trackable Drop/Visit tab, the app tried to connect to the internet and failed, showing no trackables.

Something that I've noticed in the last week of using Cachly is that the date and time that the caches were logged does not seem to be logged on Geocaching.com correctly. Here is Australia, if I log a cache in the morning, it is dated the previous day on geocaching.com. It seems that the app is ignoring the actual date and time the cache is logged and it is being logged at whatever time it is in Geocaching HQ. I then have to go on to the geocaching.com web site and change the dates on the majority of caches I have logged as they are all incorrect. Can this be fixed so that the caches are logged on geocaching.com with the actual date and time they are found?

hanks for the quick responses Nic. I realise that your app isn't designed as a GeoSphere replacement and is a different app all of its own. I'm just trying manage the transition from one to the other. I did try other apps (Looking4Cache as one example) before coming to Cachly, and have found Cachly to be the best and easiest to use as part of that transition. I look forward to having an update that will allow lots of caches to be installed. I travel quite frequently here in Australia, mainly within South Australia (about 14,000 active caches) and Victoria (about 16,000 active caches) and have become quite used to having them all available on my phone wherever I happen to be. One of the great features of that other app was that it could filter the list and just show for example, everything within 100km of the current location, which limited it to about 6000 out of the 40k+ that I often had in the database. That was really useful on cross country trips, so I'll be again very interested to see this in the new version when that becomes available. My last query about the List distances was: I go to Offline mode and select my list of caches I want (in the example I was testing, I have a list of 7606 caches - the same GPX file I emailed you earlier today from another discussion) I click on the "List" tab at the top of the screen and it shows a list of the caches in some order (I've yet to work out what order this initial list is in) If I then select the sort button on the top right and change it to Ascending Distance, the caches in the list are not sorted by by what is displayed as their distance, and I have some 18km mixed in between some 20km, and the caches that are right next to me are many pages of scrolling down the list (example screenshot attached). Thanks for your prompt responses.

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!

I had a similar issue with the new V2 version. Importing a 43Mb GPX file from Dropbox (7606 caches) of all the caches within 100Km of my home location. I can import the GPX fine if I don't try to get the images, but with the "Save Images" selected, it starts the import, it gets to image 440ish of around 3400 and the app completely crashes..