Showing the same user the same imagery sets more than once

[bgirardot]

I routinely get the same sets of imagery more than once.

I am only doing the mapping online method.

As you can see in the examples below, the only difference is that one was shown to me at 9:04 and 5 minutes later, probably 2 sets of images later, there is the exact same image. I was taking screenshots for a tutorial so luckily can prove it and not just "I swear I have seen that before... maybe not"

You will also note that they are both at the same % mapped in the set and I can confirm, it was exact the same set after this image.

[PimDeWitte]

I noticed an index was placed wrong in firebase and fixed the index. I suspect this may have to do with this issue but I can not confirm until it is verified.

If it does not fix the issue at hand, it may have to do with an updated caching behavior on Firebase's end, for which a front end fix will have to be issued. This should not be crazy complicated.

Let me know if it's fixed. If not, I will plan some time to make a front end fix.

[bgirardot]

Thank you very much Pim, I will do my best to test!

[bgirardot]

Hi @PimDeWitte @mathcass unfortunately it is still happening.

Also this is after Jess's advice to try the "bugs" button so that did not seem to help either. She also suggested restarting the app, which I have done as well.

This is after "Completing" a session and then starting to mapswipe again about 20 mins later. I can not be sure how many "sets" of imagery I went through between the duplicated sets, but not a lot, maybe 2 - 4.

[bgirardot]

So after more testing trying to see if it mattered if I was doing complete session or map further options, it does not seem to matter one way or another, I get duplicate sets using either method.

[ahstro]

This is happening to me as well, both with "Map further" and between sessions. How are non-tapped tiles handled? I could see myself making the error of making non-tapped "unseen" and therefore make the set "unseen"

[laurentS]

#49 is a duplicate of this one, but relates to the updated code, we'll post updates there.

[laurentS]

This should not be an issue any more, with the fix for #49. If not, please reopen.