Caches confused after a find

[barefootguru 67]

I haven't worked out an exact trigger, but Cachly sometimes duplicates the just logged cache to a nearby cache.  It's something like:

1. Go into a cache
2. Log it
3. Back out to map
4. Tap next cache, and it will display the name from the just logged one.  Sometimes it'll have a smiley too.

V1.x and 2.0

[hidegoseek 8]

I've noticed that also.  If I manipulate the map until the 'just found' cache is off the screen, then I can properly select the next cache.  

[barefootguru 67]

I work around it by randomly tapping on 1 or 2 other caches, then it'll fix the incorrect one.

[Nic Hubbard 642]

I had someone else report this as well. Is anyone able to find steps to replicate reliably? I have been trying but can't. Want to get this fixed ASAP.

[wwbd 9]

I was just browsing and saw this topic. I had this happen to me a few times over the weekend and thought I was just fat fingering the icons

[Nic Hubbard 642]

1 hour ago, wwbd said:

I was just browsing and saw this topic. I had this happen to me a few times over the weekend and thought I was just fat fingering the icons

Still trying to figure out how to replicate this...

[barefootguru 67]

Possibly related to saving the log entry offline.

[barefootguru 67]

Saving offline didn't trigger the bug today.  The other actions I regularly do are to insert the Owner Name keyword, and after submitting going back to other logs before completely backing out of the cache.  I regularly switch between live caches and an offline list.  Still working on finding a consistent trigger 

[ShammyLevva 4]

This happens to me regularly it appears to be related to the previous cache icon being on screen - the solution is always to zoom in until the one I want to change to the only one visible then click and it will always then open the right cache. Note it only seems to happen when I've logged the cache to upload later.

[Nic Hubbard 642]

15 minutes ago, ShammyLevva said:

This happens to me regularly it appears to be related to the previous cache icon being on screen - the solution is always to zoom in until the one I want to change to the only one visible then click and it will always then open the right cache. Note it only seems to happen when I've logged the cache to upload later.

Are you able to replicate this reliably? So far I cannot and it has been hard to track down to fix.

[ShammyLevva 4]

7 hours ago, Nic Hubbard said:

Are you able to replicate this reliably? So far I cannot and it has been hard to track down to fix.

Unfortunately not. I've spent a while trying but as ever when you try to get an elusive bug to appear it never obliges. I will of course log it as soon as I can narrow down causes.

[bloodycool 5]

I also have had this happen to me on occasion since I started using Cachly (from version 1.something). It happens to me once or twice out of every 3-4 hours of continuous caching. I also cannot recreate it reliably, it just happens sometimes after I log a cache (saved for later) and go back to the map screen and try to select another cache. As previous people mentioned, I just mess with the zoom level until it lets me select the cache I want. 

[ShammyLevva 4]

I'm sure of the following.

It occurs after saving a log, not submitting one.

Once it closes the window and you view the map again what you are wanting to do is to click the next icon in the series. Now here is where the lack of repetition comes in. It is something to do with either the number of icons on screen or the proximity of the icon to the one you opened. Something that is determining what details to show in the pop up.

Whatever it is when it occurs clicking anywhere opens the last cache. Note I do not for a minute think as per original poster that it is copying the cache details. I simply think it has cached the last cache details in a variable and the click is opening the previous cache. 

The fix is to zoom right in so that only the cache you want is visible this seems to be enough to force the variable to be set to the right cache. 

To fix I'd focus on anything that stores the cache clicked, or any proximity thing to make the selection of a cache easier. Specifically anything that would be affected by a zoom limiting what cache it could be when you click on screen. 

 

Hope this helps. Clearly from the user groups comments it's quite a common bug. 

[Nic Hubbard 642]

7 hours ago, ShammyLevva said:

Hope this helps. Clearly from the user groups comments it's quite a common bug.

Thank you. I will start extensive testing on this very soon.

[CoakleyClan 0]

Hi Nic,

I created an account here just to confirm what ShammyLevva has said. I've noticed that this behaviour is occurring when saving logs - not when sending them straight away. I've not found any common variables in my experience that leads to the bug, only that it happens after I've saved a few caches for that day in a row, i.e. it doesn't occur after the first one. Perhaps if you log a few caches (saving, not sending) in a row in the same area, you'll be able to trigger the bug?

Andrew

[Nic Hubbard 642]

4 hours ago, CoakleyClan said:

Perhaps if you log a few caches (saving, not sending) in a row in the same area, you'll be able to trigger the bug?

Thanks Andrew, appreciate this extra info. Will continue to do testing.

[HikingSeal 7]

For what it's worth, I too have experienced the problem. I'll try to keep an eye out when it happens again to see if I can replicate it. I superstitiously attributed it to my phone being nearly out of memory or having too many apps open. No real support for that thought as I didn't check my memory at the time.

 

P.S. Nic, if you don't recognize the handle, this is Chris Rock.  We've been chatting about my local event and the Maritime Mega.

[Nic Hubbard 642]

13 minutes ago, HikingSeal said:

P.S. Nic, if you don't recognize the handle, this is Chris Rock.  We've been chatting about my local event and the Maritime Mega.

 Thanks. Appreciate you trying to help with this issue too!

[HikingSeal 7]

I have a little data to add. It happened to me three separate times over Memorial Day weekend. Twice using the live map, once using an offline list. In all three situations I saved the log rather than sending. No matter what cache I tapped after hitting Done on the log screen the information for the cache I'd just logged came up. The problem was resolved by hitting refresh.in the live map or closing and reopening the app when offline. Again in all three instances, it did not happen for the next cache.

I couldn't replicate it at will either. Hopefully the observations will help.

[Nic Hubbard 642]

46 minutes ago, HikingSeal said:

Hopefully the observations will help.

Thank you!