Nic Hubbard

Thanks. Will look further into the error.

Interesting suggestion. Yes, this would be possible since that data is available in the location data form the GPS chip. There would have to be a warning/explanation for users if this was the case since it would no longer behave like a compass. This would take some extensive testing, but I do think it would be possible.

Cachly doesn't support this right now. We haven't yet implemented this because it would require background location updates which take more battery. We have this on our list for adding in the future.

Strange. So this was just on first load and it works fine now?

The gear icon should turn green if you have any search filters turned on. Was this the case?

It looks like geocaching.com no longer allows slashes in usernames, which is a good thing. Usernames that already have them obviously won't be touched.

This is in More, then Settings. Is this what you were looking for?

I just looked through the API and it doesn't seem like this is possible.

You can do this in Cachly. Just tap the current location button to cycle though follow modes. These are completely different in Cachly because the official app uses privates API's for their lists. They allow creating of lists (bookmark lists) from their app that are then created on the server. They don't give third-party developers this ability. This was a distinct decision to make Cachly work how it does and keep it different from how the official app works. It works much more like the classic app in this regard. I guess we will just have to agree to disagree as I think this is something I dislike the most about the official app. Happy to discuss anything else!

Sorry for the late reply. I think all questions were answered. Was there any missed that I need to answer?

No, not only while navigating, on any map screen. So the live map, Offline map, navigate map, will always have Location Services turned on.

No, these errors will be caught on the server side and shouldn't be an issue. We will make sure to test adequate testing beforehand.

No, we haven't fixed anything pertaining to this issue, and it wouldn't be a Groundspeak thing. Strange! Maybe it would an obscure bug, let me know if you see it happen again.

Accuracy can be greatly effected by a number of factors as you said. With each new iPhone that has come out the GPS chip has been more accurate, so if she was using an old iPhone 5 it could perhaps having worse accuracy. However, I have never seen issues with accuracy and many users have commented about how excellent and accurate Cachly is. You can tap the current user location and it will show what accuracy you are getting from the GPS. I just tested it and was getting +/- 5 meters. Cachly uses MKMapView location updates for the green current location indicator. We also use the standard CLLocationManager with kCLLocationAccuracyBest and kCLDistanceFilterNone for various places in Cachly. These are all turned off on non-map screens to save battery. It would be hard to know specifically why that user felt that Cachly wasn't accurate, but if they were comparing it to a GPSr then it would be no comparison. The chip in the iPhone cannot compare to that. I haven't seen this either, but I guess I have never hopped out of the car and gone running for a cache. My caching involves helping the kids get out of their car seats and getting them ready to go before we can go looking. What iPhone do you use?

Yes, it will go into effect on May 8th.

This email was sent to all API partners. I have sent some further questions to clarify some things, but overall I hope that these will be good changes for users.

Great idea. Will do!

This isn't a seach by Cache code option. That is always available when this option is off. This search by cache name is just that. A search for the name of a cache within a 50k meter radius. (API limit)

Nope. Glad we got it figured out. Thanks @Team DEMP!

Have you tried resetting your Search Options?

Can you send me debug data? Just use the contact support option in the More tab. Also, try clearing the search options, you shouldn't have to do this, but I am not sure why this is happening for you.

That search worked for me and took me to Dallas. Your map should have moved to the location before even making a request for caches, so that is strange. Does this happen each time you search for a zip code?

I think this comes down to personal preference. I will make sure to make a note of this so we can evaluate the request.

Yes, you can just enter that into the Live tabs search field and Cachly will take you to that location.

Strangely in iOS this is no easy task to do for an entire app. However, a friend of mine Gary Slinkard had also requested this a while ago, so I have completed development of this feature in my current alpha version.