Nic Hubbard

We have not had any reports about this. Cachly passes your local timezone to the API which then uses it to calculate your correct time. If this is the case, then I am not sure what has been causing it, we have not changed anything in Cachly and I wouldn't expect an API change on a Saturday. Can you replicate this issue?

Can you replicate this on a newly saved cache though? There was a bug a long time ago that caused this issue, and if you have offline caches that are very old this might be still the cause.

What version of Cachly are you using? Are you able to replicate this issue on another cache? I just tested this and I cannot replicate.

Thank you for the suggestion! We will make sure to evaluate how other users might also use this feature.

Cachly has required iOS 10 for over a year now, but the previous version continued to work. However at the start of June the old geocaching.com was shut down which the old 3.0 version used. We don’t have any control over this and the only thing we are able to do is encourage users to update to iOS 10 and a device that can support that. Very sorry about that, but it is out of our control.

What country are you from? This is the first request we have had like this. And, while we always take user suggestions and evaluate them, I am not sure if this feature would benefit many other Cachly users.

Yes, you should be able to tap the "Abmelden" button on the to right. Have you tried this?

Please try using the Logout button on the top right of the More tab. This should help!

Sorry about that!

Can you please try logging out on the More tab?

This should never be needed. Was this a Live or Offline cache? If it was offline, all you needed to do was refresh the cache. If Live, it would have updated automatically if you viewed it again.

We would love to have you! Please email support@cach.ly so we can get you started. Thanks!

The coordinates should not come up as 00.00.000, this represents a likely error from the GPS. Can you replicate this issue if you create another Waypoint on another cache?

Forgive my previous statement, what I meant was a merging in of data to the original geocache object with new data, not a text merge where new text is appended to the description. Cachly has never merged description in the sense of a doing a diff and then merging text together, it checked some conditions and then replaced the text. Can you explain the instances where this becomes a problem? E.g. the GPX contains a blank description so the local one gets overwritten, etc.? What part of the description are you not wanting to be updated?

Can you email me one of the GPX files? Looking at my file change diffs the only change was to the hint and description when importing, nothing should have been changed with corrected coordinates. Can you confirm that the caches have corrected coordinates that you are exporting as GPX?

There was a bug fix that solves an issue when updating offline caches would not update their hint and description. No other attributes were affected. Is that the issue you are experiencing?

5.2.2 has been released to the App Store.

Hmm. Something is happening in the background when you are opening the app, and I am not sure why you would get the error. We have a 5.2.2 update coming out soon with some additional fixes that should solve your issue.

This issue has been fixed. Sorry about that!

This issue has been fixed and was an error on our part. Sorry about that!

What version of Cachly are you using? You are saying that logout doesn't help?

Yes, the map type makes a difference. We are not able to replicate. Can you provide some exact steps to reproduce this bug?

What version of Cachly is this? It is a live or offline cache? Also what map type are you using?

This action isn't advisable. Think about an online form where you keep clicking submit over and over.

Translations in Cachly come from Cachly volunteer translators. Is this something you would be interested in doing or know someone who would?