Jump to content

Nic Hubbard

Administrators
  • Posts

    3837
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Nic Hubbard

  1. Good to know that seems to be the culprit!
  2. 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.
  3. Does this happen on all caches? Can you give an example GC code of one where it isn't working?
  4. 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.
  5. No, this hasn't been fixed in 5.2. It is still on our list of bugs to address.
  6. 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.
  7. 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.
  8. These filters are case insensitive. I have tested this and I am not able to replicate.
  9. There will be additional fixes for this coming in our 5.2 version. These were being caused by the new geocaching.com API changes.
  10. 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. 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.
  11. No, this isn't currently a feature of Cachly, but it has been requested, so we are still considering it for a future release.
  12. You logged completely out and then back in? This has normally solved the issue.
  13. No, we do not have a way to show that promotion like the official app does.
  14. 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.
  15. 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.
  16. In our next version, Friends will return to Cachly! Read More...
  17. So it seems to be working now? If so, there could have been an error on the geocaching.com API side that was causing the server errors.
  18. Can you verify that you did use the Logout option on the More tab, and then logged into Cachly again?
  19. Did you specifically use the Logout option on the More tab though? This shouldn't ever be needed as it will remove all of your saved data.
  20. You had said you couldn't login, so I had assumed that meant you couldn't get past the login screen. If you logout of Cachly and then login again, does this help?
  21. When errors do you get when trying to login? Can you please show us a screenshot?
  22. You said you cannot log back in, but is that working for you now? Does other things in Cachly give the same error for you such as viewing your profile?
  23. Yes, this has to do with the new API. We are hoping to push out a fix for this in our 5.1.5 update.
  24. Thanks, will look into the issue.
×
×
  • Create New...