Nic Hubbard

Don't worry. I won't remove it. Not a problem. Keep it coming!

This keyword is proving to be very frustrating. I am almost tempted to remove it since it is such a tricky one to make work correctly. Thanks for the comments, I will add them to the bug report and work to fix it.

I have fixed this issue, with help from Clyde from GSAK. I will push out a new beta with this fix and Settings option. It will be in 2.0.2 so we will have to wait for Apple to approve the beta, which is pretty quick.

Thanks, I will look into it as well.

You need to be using 2.0. If you are, just swipe the row on one of the PQ's that is in the Offline tab. Then choose "Options". This will give you options to copy, merge etc with another list.

Welcome to Cachly! This has been requested by other users, but in looking at the various API methods that we have available to them it doesn't seem like an easy thing to do. We are still investigating this. Cachly has this. Just go to Settings and you will see the log defaults option. You can also insert keywords for various things.

You can now vote for feature requests. This will help us to know how popular suggested features might be. Please vote!

Is this only happening for field notes? Or also for published logs from Cachly?

I have been talking with Clyde from GSAK about this issue and seeing how they fixed it. He has some great insight has he has been dealing with this since 2011 or maybe earlier. He provided some links with much more background on this issue: http://gsak.net/board/index.php?showtopic=17802&view=findpost&p=126030 http://gsak.net/board/index.php?showtopic=16698&view=findpost&p=116316 http://gsak.net/board/index.php?showtopic=16063&st=0&#entry111704 http://gsak.net/board/index.php?showtopic=19146&st=0&#entry137891

Are you force quitting Cachly, or is iOS doing it when it needs memory? Saving application state is something that is on our list. Working on feature priorities right now for 2.1 so will see where that comes in.

Having it open in Safari is a quick fix and I think that there are good arguments for this, so I will get it fixed right now. Won't be in 2.0.1 as we have already submitted that, but will be in 2.0.2.

There isn't currently a way to view more than one PQ at a time, but you can merge lists so that you can create a "master" PQ list. Just make sure you are using version 2.0.

Yes, this is a feature that we have been planning for a long time, but it just didn't make it into 2.0. It is now planned for 2.1 which is now being worked on. Stay tuned!

As you mentioned, it is a hard thing to keep track of. Are you using version 2.0? In 2.0 there was a number of fixes to make this keyword more reliable, but as you have stated there are still issues. I will look into it right away and get it fixed.

Happy to help!

Yes, I think adding an option with a big warning about this is what we will do. Still working on the specifics, so it might not be for a little while until we release that version. Thanks for everyone's input.

This option will actually need to come after 2.0.1. Working now to schedule it.

You are using the beta.

Yes, this feature is being added in 2.0.1. It is currently just a "quick search" and not the full filtering functionality that we will be adding in 2.1.

This possibly could be the case for very old logs. It might be that very old logs are not UTC. There is a Time Zone settings already on geocaching.com, but I really don't know what it affects. Would be curious to know.

I do not think that it would require updating all data. From what I have seen personally in the API and been told by the Groundspeak developers, the log dates are clearly stored as UTC dates. The real "bug" on geocaching.com is that it isn't taking the users set time zone into account and doing a conversion from the UTC date into the users localized date/time. Jason, one of the Groundspeak developers told me he put it on their list and they will be looking into the issue.

After doing more testing, and thinking about this more, I have come to the conclusion on a few things: Geosphere is doing UTC timezone manipulation to appease geocaching.com. Cachly is sending the correct UTC time for the log date. UTC time is the same in every timezone on earth since it is a calculation of seconds since 1970. geocaching.com should be taking the UTC time and converting that to the localized time zone set by the user in their geocaching.com settings. This is currently not happening. If and when geocaching.com fixes their UTC date issue, all manipulated Geosphere logs will be incorrect. If Cachly manipulated UTC dates based on the timezone, when geocaching.com fixes their UTC issue, these dates would also be incorrect. With those points in mind, I will be keeping our logging date the same. I don't want to manipulate the date so that geocaching.com "looks" correct, but the UTC date in the database is incorrect. Thoughts?

There hasn't been a date set. We are just finishing up 2.0.1 and will be starting work on 2.1 very soon.

Thanks guys. Will report back in a few hours when I get a chance to test everything again and some new time zone offset code.

Will do. Will be later tonight my time.