barefootguru

Cachly does make its entire database available through iTunes (device > File Sharing > Cachly > Cachly.sqlite), and I suspect the DNFs will be in a separate table, but you'd have to know SQL to go that route. Personally, even the living aren't that interested in my hobby p.s. looks like you can get a list of DNFs which haven't subsequently been found with GSAK https://project-gc.com/qa/?qa=8983/search-dnfs-not-subsequently-found, which could then be exported.

You can see your DNF logs through the website, though it also includes those you’ve subsequently found. https://www.geocaching.com/my/logs.aspx?s=1&lt=3

I think there's a date bug in the Date Downloaded filter, maybe because I'm in New Zealand… and currently on daylight saving — NZDT, UTC+13. I'm looking at a cache which says 'Downloaded on 20/02/2018 at 11:59' (which is correct). If I create a filter with Type=Date Downloaded, Date=19/02/2018, Logic=Earlier than or on, Invert Filter=No; then I still see the cache. If I change the date to 18/02/2018 then it's hidden as expected — so 2 days out? Cachly 4.0.1, iOS 11.2.5

I just refreshed the list in chunks, using Visible Caches, and it went fine — thought it might be a bad cache.

This may be the opposite of helpful I'm still running 3.1 on my iPad, with the same list of offline caches, and it's still updating fine. Could it be the image downloads?

Since Cachly 4, I'm no longer receiving the waiting message when updating (pretty much) the same set of caches — so it's definitely slower

FWIW, I deleted and reinstalled Cachly, redownloaded My Finds, and same crash occurs. Have e-mailed that log too.

Should it start with Cachly? The only ones I can see are Cachly.cpu_resource… I've just e-mailed the latest of those. The timestamp looks around the start of the update rather than when Cachly crashed though. BTW it's actually significantly slower now: I wasn't timing but it's gone from 5-10 mins to 30-40 (before it crashes).

Any thoughts @Nic Hubbard? This is a regular part of my workflow to add my cache notes to My Finds.

It didn't happen on another smaller list. I deleted the list and redownloaded — a My Finds PQ. Same thing when updating all caches. Updating just 1 or a small number of visible was successful.

Since upgrading to Cachly 4, it crashes when updating one of my offline lists: around 2000 caches, doing a full update of all caches. Cachly takes about the right amount of time, then crashes. Could only find Cachly.cpu_resource logs in Analytics, not a crash… hmm, unless iOS quit Cachly because of the CPU usage? iPhone SE, iOS 11.2.5

FWIW I'm experiencing the same slower time downloading PQs. I update my iPad — still on previous version, and iPhone — on latest version, at the same time, so it's not a network issue. The 2 devices used to take about the same time, the iPhone is now significantly slower (twice as long?)

I spend 15 minutes a week keeping my 'Unfound' offline list updated from pocket queries: I have around 3,000 caches which covers an area ready for any spontaneous day trip — I can use it to both move around the map and caches are stored locally in case cellular service is unavailable.

Cachly’s Corrected Coordinate is the same as the one on geocaching.com when you click the pencil icon next to the coords, so everything plays nicely together.

I think you need: if starts with ^ remove it if ends with $ remove it add .* to start add .* to end I can't think of a situation where that'll throw the RE out, but as @rragan says, it's a complicated beast (Was responding to Nic's earlier post which has been deleted)

Yeah, Google (actually DuckDuckGo) confirms that NSPredicate has to match the entire string. I do think this will trip people up, as no ^ $ is present. I like @rragan‘s idea of stripping ^ $ if present and enclosing the string in .* but maybe that’s too complicated, and an explanation on the screen saying the expression is automatically enclosed in ^ $ would suffice.

@ACME WildCachers The special My Finds PQ always includes your own log(s)… and no others. AFAIK Cachly merges/combines the log entries when refreshing.

@rragan I run the special My Finds PQ and import that into an offline list — contains every cache I’ve found with log. Then I update all caches with full cache data to have my notes available offline too.

Thanks Nic, will submit the feedback to Apple.

I do a lot of walking and use the map scale heavily. I miss having it constantly onscreen in the latest version of Cachly; and find it clunky to have to pause a zoom to see it for any period of time.

Cachly has a handy feature, that when you select a cache pin on the map, and view the details (e.g. log), then tap the back arrow, you’re returned to the map screen with the cache still selected — it still has the summary details ‘balloon’. But if one of your actions when viewing the cache is to edit the personal cache note, when you return to the map no cache is selected — so you can’t tell what cache you were looking at. (Offline list, offline map)

A minor bug, possibly only for us folk so far ahead of UTC (currently +13): today’s the 27th a find log submitted through Cachly, with the default date of 27th view the cache summary page from the Live screen, and the logs will say ‘Tomorrow’ go into the logs, and the last find shows today’s date (27th)

I usually work with offline maps, which means I can only see a single country. If I go into the Trackables screen and select View Travels, most of the map is blank, and you have to switch back to Live/Offline screen to change it. Would be handy if View Travels map had the same map selection icon in the bottom right as the Live/Offline screens.

Not using Cachly to navigate seems a pretty niche use of it. You could turn off Cachly’s GPS access in iOS’s privacy settings.

I have 7 lists, but that jumps to around 15 when I'm doing PQ imports… which I then merge. It's behaving for me now too. I wonder if it was triggered by importing PQs and a My Finds, and restarting Cachly has fixed it?