Nic Hubbard

8 hours ago, AnTsInRpAnTs said:

Will await the update. Thanks Nic.

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?

On 8/2/2019 at 6:40 PM, GoldDogs said:

Whoa! It is the latest update- but Maybe it’s because I’ve been looking at Offline- when I just check Live- it seemed to work!!! Does that make a difference???? Thanks! 

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?

On 7/27/2019 at 12:28 AM, quersumme said:

Until now, I have always pressed the button quickly so that all caches are downloaded as quick as possible...

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?

19 minutes ago, thebedfords said:

Interesting!  Tested without WiFi and I have pictures!  Switched it back on and they’ve gone again. 

Good to know that seems to be the culprit!

This isn't an issue we can replicate or have had reported before.

That being said, can you test this when NOT using wifi? I am wondering if for some reason your wifi is blocking images from the geocaching servers.

Does this happen on all caches? Can you give an example GC code of one where it isn't working?

It looks like the issue is that the degree sign is actually not a degree sign, but rather the masculine ordinal indicator. See: https://en.wikipedia.org/wiki/Ordinal_indicator under the Usage section. Checking the unicode of the character from Cachetur shows that this is true.

I will make sure that Cachly can account for this in future versions.

No, this hasn't been fixed in 5.2. It is still on our list of bugs to address.

Thanks for the suggestion!

On 7/15/2019 at 11:21 AM, markens said:

When importing a gpx file into an offline list, first check to see if the gsak user flag is set for *any* cache in the set.  If so, then that implies that the lack of a user flag is also important.  Therefore, set highlight for caches with the user flag set, and *remove* highlight from caches with the user flag not set.

This would cause quite a bit of confusion with users as to why their highlights were removed. I could see there being a specific user setting for this, but currently we don't have plans for that.

17 minutes ago, barefootguru said:

I just tried on a 2nd device:  cache 'GC397JN Xeyr cache burada yoxdur' in my offline list has an owner of 'Skindo'.  If I set the filter to Owner Text Matches 'skindo' it disappears.

In this specific case you are using the MATCHES operator which is a regex style match, so this would be cast sensitive. You would need to do a specific regex case insensitive match like

(?i)skindo

 in order to make this work.

You can use a different operator like Begins with or Contains to ignore case.

These filters are case insensitive.

I have tested this and I am not able to replicate.

18 hours ago, barefootguru said:

I thought this might be triggered by the usual annoying ¿monthly? re-login that geocaching.com requires, but the device I had to reauthorise 2 days ago just needed the same fix again.

There will be additional fixes for this coming in our 5.2 version. These were being caused by the new geocaching.com API changes.

19 hours ago, markens said:

From what I see, the highlight attribute persists in the database even after the cache has been deleted from all offline lists.  And so that same attribute is applied when an affected cache is seen again in an online search, or added to an offline list.

This is correct. Highlights are not local changes, they are globals changes that are synced to iCloud for use on all your devices. Since they are not saved in the database, they are used for Live caches. In the same way you can also highlight and online cache and it will be highlighted offline.

19 hours ago, markens said:

But it would be useful to be able to remove the highlight attribute from all caches in the offline database, to prevent them reappearing again on new searches.  Is it possible to do this?  Other than deleting the app and reinstalling?

Yes, you can do this. When viewing an offline list, tap the ... button on the top right and choose Highlight > Remove Highlight > All Caches. You can also go to the More tab then Highlighting where you can remove all highlights from everywhere in the app.

No, this isn't currently a feature of Cachly, but it has been requested, so we are still considering it for a future release.

26 minutes ago, Silyngufy said:

I too am having the exact same issue. All I get is an error code.

You logged completely out and then back in? This has normally solved the issue.

No, we do not have a way to show that promotion like the official app does. 

11 minutes ago, thelinuxnoob said:

Makes sense. I have a small correction though, they don't have push notifications from the app. You can get an email notification sent via text message if a cache is placed within a predetermined radius of a specific location. That's the part I find sort of inconvenient. I had hoped to be able to simply enable a setting that would notify me if a cache was placed in my vicinity.

I don't use the Official app, but I had thought there were notifications, but I could be wrong.

When you get the email, you can long press on the link and copy it, then paste that into Cachly's search field and it will load that cache.

Unfortunately no. There is no way of Cachly knowing if a new cache has been placed since we are only a third-party authorized partner app. Meaning we don't have direct notifications from the geocaching.com server for things like that. 

The official app can do this since they have push notifications built for their app that come from their server.