Welcome to the Bug Reporting page! Please refer to these tips when submitting new bug reports:
1. Browse the known issues section or check if another user previously posted about a similar issue.
2. Upvoting posts help us understand how many players are experiencing the bug.
3. Refer to the Best Practices to learn how to write a bug report.
4. File each issue separately if you’ve encountered multiple issues.
1. Browse the known issues section or check if another user previously posted about a similar issue.
2. Upvoting posts help us understand how many players are experiencing the bug.
3. Refer to the Best Practices to learn how to write a bug report.
4. File each issue separately if you’ve encountered multiple issues.
Comments
The amount of things left out of the duplicate page is downright ridiculous in some cases.
This one appears normal but a look at ingress shows that the only waypoint missing from the duplicate map is the actual duplicate of this current submission.
This is an interesting case. 2 waypoints are missing from the duplicate map but it also shows one that is in lightship but not in ingress. The lightship only waypoint did not sync to ingress even after the daily sync so it is not a new waypoint.
I have cases now where I look at the duplicate and switching back forth to make sure it is actually a duplicate, when it disappears.
closing the window and reopening does not make it reappear.
I wonder if it is a cache problem
In this case the only one missing from the duplicate check is the actual duplicate. These are going to cause so much mess in the system when they get approved.
seems to be the other way, too. Some POIs are missing on the Intel.
Is this fixed? I haven't run into one yet today.
I haven't encountered this in a week or so, but just got a very bad (or good?) example:
review:
Intel map:
It just happened again to me today. And the nomination is a duplicate of a missing wayspot.
Not only is the crucial wayspot missing, on reload, another nearby wayspot dissappeared.
Nomination location: 5.208165,100.696026
Location of existing wayspot missing from Wayfarer: 5.20821,100.696167
Wasnt aware of the problem, but noticed one yesterday (March 1st)
The gps coordinates for the place are 55.704331,12.430525. Two close by POI wasnt shown under duplicates.
Hope Niantic will look into it VERY soon and would also be nice to get a respond about how approved duplicates will be handlede.
Isn’t it interesting that when they start processing the appeals, bugs happened. A coincidence I think not. Still waiting on my missing portals to appear.
ditto, it hasn't migrated since 02/28? tonight 2 other portals have not migrated ... it's abusing!
Hi @ChristinaRS2610-PGO, thank you for sharing. Are you still noticing this issue?
I observed missing duplicates today...
Refreshing made it worse (another dupe disappeared).
I came here to say this is happening again and see that an Ambassador has also noticed it.
Edit: I can now confirm that it is happening regularly even without refreshing.
Actual duplicates are not showing on Wayfarer but a check on Ingress Intel shows that a duplicate already exists. It would be impossible to review like this.
I've experienced this too a couple times over the past couple days. The first time I saw the bug, it stood out to me because it was a Wayspot that I had personally created that wasn't appearing on the duplicates map. I panicked and worried that someone wrongfully removed one of my favorite Wayspots that I made.
I just had this happen as well. I was reviewing and I came to this nomination and saw that there was a playground in the Nearby check right next to the nomination I was reviewing. I switched over to the Contributions page to check something and then when I came back to the review page I had only 1 nearby wayspot. There are 14 portals visible in this area on Intel but only 1 wayspot in the nearby check. I tried navigating to other pages and then back to the review page, I logged out and back in, closed and reopened the browser but still only the 1 will load.
@NianticGiffard this bug seems to have resurfaced possibly in the 4.8.9 release. can the team take another look please?
Thanks for bringing it to my notice. I have escalated it to our concerned team and will follow up once we have updates to share.
I got this windmill for review. I know there is a duplicate of this existing wayspot because I remember duplicating it before.
Look at the Location accuracy tab and then check Intel (below) and the Lightship map:
The link to the existing Windmill:
How am I meant to duplicate this when the map doesn't even load? This issue seems to have resurfaced again...
I thought something may have been up. I've been reviewing and seeing areas that I'd expect to have lots of Wayspots (big UK cities) but there's hardly anything showing on the duplicate map. I'm now wondering if this is why my rating has fluctuated recently as well, as it's possible that I may have inadvertently been voting to approve/reject things that already existed, rather than correctly marking them as a duplicate due to the duplicate not actually showing on the map. Maybe I should take a break from reviewing until it's fixed.
@NianticGiffard is there any update on this? it's a pretty impactful bug to go unfixed for several months, occasionally it even results in exact duplicates not appearing on the map. this is hurting people's ratings.
When doing reviews, I thought it was odd that this park showed no POIs on the duplicate map.
When checking the intel map, I saw that there are actually numerous POIs in the park!
This bug is still not fixed and I feel like it's getting worse. It used to just happen to a couple Wayspots on the map; but now it seems like nearly every Wayspot disappears from the duplicate maps.
6 months later, the bug still exists
Like with all things, this issue has been escalated with the "concerned team" who have all been recently laid off due to Niantic budget constraints.
I've had to dupe things to erroneous things simply because the actual existing dupe did not appear, even after logging off or refreshing.
Yup, seeing the bug again. Or maybe the bug was never fixed and has always been around.