Nic Hubbard

Yes, we have decided to not change how it currently works.

I have tested GC4C3D8 and it imported correctly into GSAK. Can you send me the GPX that is having issues?

I have tried to replicate this many times, including today driving from an area with excellent service, to the National Forest with no service. Cachly had no issues with following my location. I have also tested this hundreds of times over the last 5 years, so it is for sure a tricky thing to debug. I think the one thing to try is to quit Cachly. Possibly if there is a Location Services bug in iOS that would help it to start using GPS rather than just cell tower triangulation.

They just don't show up on geocaching.com. Wish they did!

Waypoints are part of the geocaching.com API. They are synced with the API server and can be seen in any API apps that support that feature.

When you save offline, you can save Lite caches and it will save those instantaneous since it already has that data from the search. If you want full data then that has to be requested from the server, 50 caches per request since that is the max the API allows. This is the same limitation that any other API app has.

I am not sure what you are saying here. What action are you doing that takes 20 minutes? Cachly does use a true database. If you are not happy how it works please let me know how we can make it better.

Thanks, will look into this.

No. The security implications of us saving users passwords is not something we want. This is the reason why OAuth is used and connects with Groundspeak, so we don't have to save passwords. In 3.0.3 when you are asked you re-authenticate you will be asked if you want to Logout or Cancel. You can cancel if you need to continue using Cachly. Previously it would log you out without any option.

Correct. We never know your password, and do not want to know them. We only hold the auth token in the iOS keychain.

We use what iOS provides, so it isn't something that we have "designed". Will see what we can do to make that stand out more.

You shouldn't have to use any tricks to keep GPS working. Was that the issue is that GPS stopped working and you couldn't see your current location?

What issues are you seeing?

What was the issue here? Had you saved caches offline?

Cachly does currently do this, so I will have do some some checking into this specific issue. Thanks for reporting!

GPX export has been greatly improved in our 3.0.3 beta. It removes the issue of an empty waypoint at each cache (this was the original coordinate waypoint), cleans up a log of the code and gives you export options. Will look into moving to 1.0.1 and will do some testing in GSAK to see why it is showing the error about no/code ID. Thanks for reporting!

Yes, filters based on dates will be coming soon.

Did you choose the "full" download option? As for the hints, was this a cache that didn't have a hint?

I would't think this would affect anything unless there was a deep bug in iOS. That setting only changes a true/false value in the compass API for iOS.

Sounds like that isn't a supported option through the API. Will ask Groundspeak about this.

Will ask them. Thanks for your update.

That is great to know. Just strange that some have had an issue...

I have had two users report this issue that their phones were not able to find their current location when in an area with No Service. Switching to another app worked correctly and found their location. Has anyone else had this issue? I tried to reproduce this issue on a hike up Mt. St. Helens with No Service but Cachly worked perfectly the whole time and there were no issues with GPS. Just trying to track this bug down...

I will for sure consider this. The pending logs screen items are starting to get cluttered so I need to take that into account.

This is going to be a Settings option in the next beta. I don't want to force changes like this on users when they are not used to it.