Kelsoboom

My most recent experience was GCZQ02. I had previously logged it as a DNF, and all the other caches in that immediate map area were logged as finds.

I will try, but what makes it difficult to repeat is that it seems to be triggered by logging a find on a previously unfound cache. So that means that once you make it happen once, you have to find a different cache to make it happen again. But I'll try to see if I can find an instance that is reproducible.

Sorry I didn't respond earlier, but I'm happy to report that the waypoint problem I reported is not an issue with 2.0. I see that in the new version, cache waypoints and user waypoints reside under different list headings, but all of them are there when I look for them. In fact, I was a little surprised to find that not only were the user waypoints I had just saved now properly displayed, but it also showed the ones I had saved days before. So I see what you mean when you say that the PQ downloads come with more information than before! Anyway, all seems to be well now with this issue. At the risk of maybe causing confusion, I'd like to use this thread to bring up another unrelated (I think) issue that I've noticed. It is similar to something I'd noticed previously with 1.1.7, but hadn't got around to reporting before 2.0 was announced, but now that 2.0 is out and the bug is there, I guess I'd better mention it. I was out caching today, looking for a cache I had previously DNFed. Because of my previous DNF log, the map symbol was a blue frownie. After successfully finding the cache, I logged my find and went back to the map expecting to see the symbol changed to a smiley. But not only was it still a frownie, but nearly ALL of the smileys on the map were now displayed as frownies. I tried refreshing the map, but it didn't change, and even if I panned the map to a completely different location and refreshed, most of the symbols that should be smileys were blue frownies. The only way to restore the display to normal seemed to be to force quit the app and restart; after that everything was back to normal. I'd classify this as a non-critical bug, but I figured you'd want to know about it, if it has't already been reported many times. That's all; thanks for writing and maintaining an excellent app!

I encountered something yesterday in Cachly 1.1.7 on IOS 10.1.1 that might be a bug. I was finding a cache that I had previously downloaded through a pocket query and which had four auxiliary waypoints as a part of its listing. These were all accessible on Cachly through the Waypoints menu. However during the process of finding the cache, I decided to save another waypoint of my own through the Add User Waypoint option. After doing that, all the original 4 waypoints disappeared from the list and only the newly created one was visible. The list heading still said there were 5 waypoints, and those waypoints still appeared on the navigation map, but the list only gave access to the one. I was able to recreate this behavior again when I got home.