Nic Hubbard

Just curious, how are you getting new cache notifications by text? I have never seen this option on geocaching.com.

Yes, the line will stay locked on your current location and the target cache. Sounds like there was a glitch. Can you replicate this?

I haven't ever seen those available as text message, are you meaning the emails? If so, you can copy the link and paste that into the Cachly search bar on the live tab.

Looks like you just need to refresh your lists. When on the Online lists tab, just pull down on the list and it will load new data. Let me know if this helps.

Ah, yes. I am surprised that it works at all. It must be using the GPS course data.

Let me know if you can replicate #3, I am not able to. Also, for question #1, have you tested this again? Many users use this feature.

Yes, the watch app uses GPS/Location services from your watch, it it has GPS. Is yours at least a Series 3 watch? There isn't a way to lock this mode, but it has been a requested feature. What map are you using? Going to the compass or descriptions should not take you out of this mode. I wasn't able to replicate this. Let me know what map type you are using so I can try and replicate that on my devices.

Glad it is working!

It should be working. Can you view a few caches on your phone (meaning view the details screen) and then see if it works on your watch?

It should be recognizing the current cache from your phone right away. Are you sure you have bluetooth turned on on both devices?

Thanks, this helped me find the bug. It will be fixed for 6.0.6. Thank you!

I have been able to replicate the issue in an offline list. Can you confirm that it works correctly if you search for GC8YQDQ in Live, but that viewing it in an offline list is where the problem is?

Was it working correctly before this time? Nothing has changed in Cachly with regards to the end time since 6.0 was first released.

Hmm, mine is showing correctly. What time zone are you in?

Thanks Frank. This would take significant development, but it is still something that I have on the list to consider.

This is synching the highlight database with the Cachly SQL database. Can you try turning on iCloud? This feature is meant to work with iCloud, and although it does work offline from that there might be unexpected behavior without it.

Thanks. Looks liked you are correct, it is only happening when the note is deleted completely. Appreciate you reporting this, I will get it fixed for 6.0.6.

Are you making sure you wait long enough for Cachly to send the update to geocaching.com? Meaning, if you delete the note, then return to the details screen and update the cache quickly, it is likely that the note had not been updated yet on geocaching.com, so you would get the note before the update. Also, can you let me know why you are quickly updating the cache after clearing the note? It wouldn't require an update to the cache, so just wanted to check if you were needing to do that for another reason.

Are you seeing these issues in both live and offline? Try using the manual sync option. That can sometimes fix some highlighting issues with offline.

In Settings in Cachly you can change how many caches load, and you could set that to 100. In this case it would likely solve your issue, although I still think it is a deeper API issue as it shouldn't be happening.

So, for whatever reason, the API is loading that cache in 51-100, rather than 1-50. I am not sure why, as I can't replicate it on my account. I will let the HQ developers know about the issue.

If you load caches in that area, can you tap the load button a second time (without moving the map) to load more caches in that area? Does it show the cache? In testing, this seemed to show the cache for me, while the first load didn't. It seems to be an API bug, as caches with corrected coordinates should be found at their corrected locations when searching.

In the More tab, can you use the Email Support option and include debug data? This will help me see what API calls Cachly is making.

Thanks, we will for sure consider this!

We haven't seen this issue before, so this is very strange. I am not sure what else to try here. Does this happen with any other caches?