Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by barefootguru

  1. 3 hours ago, Nic Hubbard said:

    No, this isn't true. That message is shown if you have exceeded 30 API requests in the last 60 seconds. There are instances where you would have already used some API requests, e.g. loading caches in Live, viewing an individual cache etc. that could have caused it to appear.

    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 :rolleyes:

  2. 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).

  3. 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

  4. 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?)

  5. 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.

  6. 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.

  7. 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)

  8. 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.

  9. On 10/12/2017 at 4:57 AM, MrGigabyte said:

    If we had an option to toggle on/off off the GPS completely, then that would verify why my battery drains so quickly while using the app. I only use the App for information on caches. Only rarely do I use it to navigate to them.  But as I have to use the map screen to find them, the GPS is used all the time. 

    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.

  10. Hi, when copying or merging an offline list, the list of possible offline list destinations to copy/merge the selected list into, is in a different sort order from the main Offline lists screen.  Would be easier to follow if they were the same B)

    Cachly 3.1

  11. On 11/23/2017 at 6:07 AM, ChrisDen said:

    I am also having this issue. Beta 3.1.1(2) 

    I type some of a log then insert a keyword or text template and it gets inserted at the beginning of the log, not after my text

    It's in the current 3.1, it's very annoying.