Nic Hubbard

Yes, Geosphere has access to accessing your location even when you have left the app, so it could be using GPS and battery while you are not actively in the app. Cachly doesn't do this, and only uses GPS while the app is active.

One thing you can do to give you a hint as to which apps are using GPS is to go to your iOS Settings -> Privacy -> Location Services. You will see the location icon next to apps that have recently used your location. Cachly 2.0 will be out on December 5th, so make sure to update!

I didn't meant close the app, just leave the app by hitting the home button. Closing it completely would be a huge pain for users.

Thank you! Please let me know if you have any other questions.

Correct. You can even test this by being in Cachly, then locking your phone. When you press the power button again (still on lock screen) you can wait until the location icon in the status bar turns off. This means GPS is no longer being used. Yes, GPS switches back on if you unlock your phone and are back in Cachly. Another tip to save battery life is to turn your phone to Airplane Mode. Since iOS 8 you have been able to use GPS while in Airplane Mode. This will also really save on battery. I will still add the GPS on/off idea to our feature list. I think it is a valid request that we will explore. Thanks!

Glad you are enjoying using Cachly! This is a tough one. I am of mindset of trying to make things powerful, while also being minimalistic. This means, if iOS can perform a function, I don't want to add it in the app (such as a flashlight feature). So, with that in mind, just locking your phone or exiting Cachly will turn off the GPS. Cachly doesn't keep GPS on while you exit the app, so this is the simple way to save battery life. When you want to turn it back on, just unlock your phone, or return to Cachly and GPS will turn back on. Would this work for you?

Welcome to Cachly! Bulk upload of Pending Logs was a feature that we wanted to add in 2.0, but ultimately we had to keep it off the list because we couldn't add any more features since we want to get it released very soon. That feature will be priority after 2.0 is released and will be in 2.0.1.

Team DEMP beat me to it! Yes, exactly as was said, this is just a feature of iOS and isn't something that we added.

Yes, as Team DEMP said, in 2.0 this will be possible to view other user's hides. Unfortunately we are not able to show Archived Hides, as the API from Groundspeak does not include those.

This isn't currently planned. It would be a huge feature integration, so we are currently focusing our development efforts on other features.

You will need to visit geocaching.com to create an account. Once you have created an account and verified it through email, return to Cachly and login. Currently Apple does not allow us to have a Signup button in Cachly. I wish Apple let us as it is frustrating on our end too!

Happy to help!

Happy to help. When you create a new Waypoint, did you enter the coordinates and then hit "Save"? Make sure not to tap the "Current Location" option or "Geocache Location", as those are just quick presets. Once you have a saved Waypoint, you can swipe that row and it will give you the option to Edit or Delete. You can Edit your created Waypoint and fix the coordinates. Let me know if that clears things up, I wasn't positive how your waypoint didn't get the waypoints that you entered, so wanted to make sure you didn't tap a preset.

Yes, this feature has been added to our 2.0 version and our beta testers have been using it for a little while now.

Excellent idea. We actually have this on our feature list, but I will bump it up in priority. Thanks!

No, those two things are not related. What I meant was, some caches might have 500 photos available for them, especially very popular historic caches. Cachly does not download all these images, it only checks the last 30 or so logs to see if images were included in those logs.

When using the "Download Images" option Cachly looks through the log data that comes from the API for each cache. If the logs that are included (normally 30 logs) include images, those will be downloaded. So likely you will only get the last few images for a cache. We don't download all images for caches because that would require a API call for each cache to find out what images are available (then downloading all images available). If we did try to do that it would quickly exhaust the available API calls that a user is allowed per minute. For example, if you were downloading 300 caches offline, we would have to make 300 requests to geocaching.com, and because we are limited to 30 requests per 60 seconds, this entire action would take over 10 minutes.

Thanks!

I had talked to one of the geocaching.com developers about something very similar (Field Notes) and from what he said, it made it sound like it works now. And that submitting from Cachly we set the UTC time, and it will show the time in your geocaching.com account based on your time zone settings in your user account there.

Do you mean as a .txt file that you would import into a program like GSAK? This is a feature that is in our 2.0 version, although it is for exporting Pending Logs. But, many of our users will create Pending Logs, then export as a .txt for GSAK. Then they will just delete the logs from Cachly.

Can you zip the file and send to support@cach.ly? If not, could you share the file URL through dropbox to that same email address?

Could you contact Support through the app and send the GPX file so we can make sure to test it in 2.0?

When is this crash happening? Any particular action you are doing that invokes the crash?

Thanks for reporting this. It is for sure a bug, and we will get it fixed.

Groundspeak limits users to downloading 6000 "full" caches per day (caches with description, hint, waypoints, logs). And 10,000 "lite" caches per day (basic info like location, difficulty, terrain, etc). Once a user uses these caches up you have to wait 24 hours to load more caches. Unfortunately this isn't a limitation of Cachly, but a limitation of geocaching.com. I wish that there was a way to fix this issue, but the good news is that most users will never even get close to that limit.