Nic Hubbard

State restoration is something that I am working on, hopefully will be part of 3.1.

I am not sure this would help. However I think turning on and off location services and waiting for a location fix would likely do the trick. I have noted this in the feature request in our internal tracker.

It does not. iOS will background Cachly, but you can resume the action if you return.

This sounds like a very bad idea. Reason being, only 50 caches can be returned at a time from the API. That means you will need to make 220 API requests which is going to take a very long time with only 30 allowed per 60 seconds. If I were you, I would break that up into smaller lists.

Are you meaning Offline Lists?

Can you explain this more? Caches can be sorted by many attributes in the Sorting menu.

When viewing the cache, tap the Trackables button that has the bug icon. This will show you the Trackables that the cache has. Obviously this is not always accurate as people don't always log their trackables, but if you do see it there just tap the Trackable and then choose the "Log Trackable" option. If it isn't in the list, but is physically in the cache you can go to the Trackables tab and search for the TB code or tracking number. From there you can choose to Log the trackable.

I built the Logs tab because it is something I use all the time and really love. I wanted to give Cachly a social media feel, where the Logs tab was like a timeline of events that you could go back and explore.

I would add this, but it isn't available in the API.

That cache isn’t Premium so you should see it. Tap the gear icon in the search field. You must have a search option turned on that is not returing that cache.

Are you a Premium member? The Geocaching.com API limits Regular users to only seeing traditional caches.

This is correct. If you are not moving at all then iOS likely won't send any more coordinate updates (once a good accuracy is returned). This is to save power.

Sort of. From much research I have done, averaging waypoints on mobile devices doesn't help all that much.

Are you able to provide the crash logs for this?

It doesn't look like the API allows this. I will check with HQ to see what the policy is on this. In the official app, can you view the full cache? Can you show me some screenshots? I don't own any caches on a Regular account so I can't test this.

This will be fixed in 3.1. No, but this won't be an issue in 3.1 due to the massive speed increases.

You can do it however you choose. I just was curious. Currently using the Cachly PQ screen will creating a new list, but if you download the PQ GPX files from geocaching.com you could import those into a single list or choose the list to import into.

There is absolutely no limit to how many caches you can add to an offline list. I have added 55k before. You are trying to import GPX files then merge them into lists?

Great news! This feature has already been develped and is in our 3.1 beta. Stay tuned for the public release.

This is something that we are working on. Not a quick and easy feature.

Thanks, it is on the list!

This isn't an easy thing to "fix", as this is the standard way that iOS maps work. To developer this we would have to rebuild the entire way that our mapping works, following the user works, and map follow with heading rotation works. It is a huge development, even though it might appear to be very simple. At this point, because of the massive changes involved, I don't have plans for this until 4.0.

Will look into this soon and report back.

Do you just mean refreshing the cache details page?