barefootguru

But the existing caches all have circles, so you just ensure you're outside them?

I believe that too, but authentication appears to be a series of web pages, so Cachly could save my password then enter it for me, or enable keychain access on those pages.

This is pretty minor 

After reauthenticating, Cachly will ignore Automatic Search on Start being turned off, and show the first 50 caches regardless.

I've posted in the GS forums the nuisance and decreased security that having to reauthenticate every 90 days represents (https://forums.geocaching.com/GC/index.php?/topic/345370-feature-request-dont-expire-access-token-after-90-days/).

Is there anything Cachly could do to make this less painful…

Maybe save my password and reauthenticate automatically?

or allow me to use Safari's saved password on the GS login screen?

I think the number only goes away when Cachly is restarted, at which point it seems to correct itself but also delete any new logs created in the meantime.

It's happened 3 times… it may be related to a log which wouldn't send — a Found against an Event, or poor cellular service.

I've been submitting individual logs and Cachly has been fine.  I'll do that for a bit longer and maybe risk a bulk submission again 

Hi, I save most of my log entries locally (Send Log Now is turned off).

Occasionally in the 3.x versions:

1. after (successfully) sending the logs to GS, Cachly still shows a number against Pending Geocache Logs and on the app badge.  Maybe only on bulk submission?
2. if I continue creating local logs, these will often (always?) disappear into a black hole after a while… maybe after Cachly is relaunched?  And the count will then be correct.

Sorry for not having more details, but this is serious and has caught me a couple of times, so wanted to raise it now.

Every new post you change what the issue is.

You said you were on 10.3.1, now you're saying the problems started in 10.3.2  I've used both with no issues.

Nik's replied about 'locking' the navigation screen in a future version of Cachly so accidental touches are ignored.

You've been told how to force a recalibration, but persist in saying it can't be done.

Sounds like your Garmin is the best option for you.

If any GPS-using program is left open, the phone will chew through battery at somewhere around 10% an hour.

At best, GPS is accurate to 5 m (16 feet), so you need to double that for the original GPS reading + the finder's reading.

Would find it handy to be able to download a low-res map of the entire world.

Thanks Nic.

Reasonably sure the first lot of duplicates was generated just by doing PQ imports… maybe different lists with the same caches in them triggering it?

I was in the bush for the 2nd set, but AFAIK had reception the entire time.

V3 is misbehaving for me with waypoints:

1. waypoints are duplicated numerous times in offline lists:  first image shows the offline waypoints, 2nd the live.
2. can't delete a waypoint… possibly because it's duplicated:  see 3rd and 4th images.
3. Cachly seems to be overriding my waypoint name if it's corrected now?  Maybe not let the user edit the title, or overwrite the title so it's obvious?

Cachly 3.0.1

Hi, not sure if new bug or just noticed…

Importing a new list causes Cachly to lose the sort order on existing lists:

1. order Offline lists using Edit and dragging them to change order
2. Import from iTunes
3. select the file to import (in this example a My Finds zip)
4. Choose Offline List
5. tap + to create new list
6. tap Save
7. select the just created list
8. tap Import
9. go back to Offline lists and the order has been changed
10. note that quitting and restarting Cachly will restore the original order

Cachly was also crashing every 2nd or 3rd import doing this, but possibly because of the 'translated' cache descriptions I was exporting from GSAK.

The count of caches in an offline list was also 0 or double (if reimporting), but that's been covered in another thread.

Suggestion:  I think Cachly should combine steps 5-7:  if you're creating a new list Cachly should select it for you.

Cachly 3.0.1 (2), iOS 10.3.2; 2 different devices.

I like the current badge as it's a reminder there's things to do — finish & send logs. This use of a badge is also standard iOS behaviour.

I would sometimes use a daily found count inside the app which showed submitted + pending for the day.

In the meantime, vote on this one  

Your phone will report the same location irrespective of what app you're using.

A phone (currently) won't be as accurate as a dedicated GPS unit, particularly under trees.  Both are bad around taller buildings.

As well as ChrisDen's advice, you should take multiple readings over different days, mathematically average them, and use that result.

Good luck!

As per first post, you can create your own caches in a GPX file.  If that's too hard, you could add waypoints to an existing random cache, and navigate to them.

Nic's already told you how to recalibrate the compass:  follow his steps 1-4 above, plus the para after that.

Are you using Navigate to Cache?  When you get close to a cache, the Compass tab is much easier to use than the Map tab.

Apple's feedback pages are explicit that your suggestion will be read but not replied to.

I'm sure Apple knows about magnetic and true north   Maybe you struck the wrong guy or were talking at cross purposes.  e.g. The iOS Compass app can be switched between true and magnetic north.

Was still timing out for me about 12 hours ago.

Apparently you can force a recalibration by turning Location Services off & on.  https://apple.stackexchange.com/questions/257005/how-to-see-compass-accuracy-and-recalibrate-the-compass-in-ios-10

Apparently it's caused by geocaching.com, you just have to keep retrying.  The image downloads are for the caches that have been download.  I think Cachly could handle it better and Nik's aware of that.

When a user has added better coords to their log, Cachly adds an option to the ellipses menu to copy the coords.  Would be great if could easily use them to navigate — maybe an option to navigate to those coords, and/or ability to create a waypoint from them.  Currently I manually transcribe them to a waypoint and navigate to that.

The date might be the PQ date… whenever I download a new PQ it always goes to the top of the Offline list (as Nik says).

Tap Edit to arrange them in your desired order.

3 hours ago, Nic Hubbard said:

I have been talking with a user from Australia who has been testing this, and from his testing turning off the "Log Date Correction" option in Cachly and just logging the date normally with make dates work correctly. It seems that Groundspeak fixed things on their end and the date correction is no longer needed.

I'm in New Zealand and my Cachly logs now default to the correct day, instead of lagging a day if submitted before 19:00 (Cachly date correction is turned off).

Feels like GS is going in the wrong direction by removing what little timezone support (UTC) they did have.

Be interesting to see if they handle finds around midnight now and during daylight savings correctly.

The last month I've noticed PQs sometimes timeout before they've completed downloading… though today's batch has been fine.  And the actual download speed has been about the same.  Nothing else to report despite regular usage.