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
@Cosk62-ING Thank you for the HP:WU release notes link.
It seems I'll just continue accumulating my Dark Detectors. A pity.
Tbh, this has gone from beyond a joke to a complete and utter farce. @NianticCasey-ING is blaming HPWU team, HPWU team barely acknowledge the problem. The fact this is the 3rd or 4th (I’ve lost count it’s that normal now) shows how little either team want to take responsibility.
The old adage of “if this was pogo, it would be fixed in less than 24hrs” is true.
Tweets advertising this framework, for other games, by Niantic in the last few days is complete brass neck!
@NianticCasey-ING its been months, time to provide answers
This, this a hundred times.
I had no answers from HPWU team and from 2 weeks ago, WAyfarer teams completely stopped answering about this too, what is going on?
Game just had a major update, many people are playing again, actively, so why HOLD SYNC UPDATE even longer??? I don’t see the problem why is it so hard to release a new sync, since is the 5th time.
Is not that hard, at this time it seems only a matter of who is holding the sync, Niantic or WB?
I did not see Casey, or anybody else from Niantic, blame WB for this (I assume you mean WB when you say "HPWU team", as they are the only one acknowledging the problem). Did I miss a post?
[There may also be a team inside Niantic responsible for supporting HP:WU, but I don't recall Casey blaming them either].
not only hpwu team, but Casey have several replies about this in several threads acknowledging the situation.
it is a problem, but who should resolve it? No one seems to care enough to actually get their hands on the problem and solve.
why? Because wizards can’t submit/review? Well the wayfarer front page sometimes showcases a AR map of inns and fortresses, can you take that down too? At least we would understand we are OUT of the wayfarer mapping, ever since sync seems not to work for 2months already.
oh and another point, a lot of wizards have ingress and pogo accounts, I myself am L13 and Lv40, so I would love to see my improvements to the mapping in HPWU too, not only the ingress motherhood and pogo money making games.
sorry for the salt, but this is beyond acceptable, none of this delay would happen if the sync of both said games stopped for a day or two...
I used to nominate and review constantly (through my pogo account), but have stopped since this glitch. It's a complete waste of time until they fix this.
I can see that this is still being investigated these many months later. Any further updates?
Bumping this because it's ridiculous that it hasn't been fixed yet.
this, so much of this.
i even fully stopped playing some time after the skills/bonus updates. Really enjoyed the revamp of the system, but still, really? NO MAP UPDATE AT ALL?
its disturbing to watch people **** other games and no updates into HPWU
HPWU is treated like an unwanted child. Sad but true.
Niantic didnt even try to think of an original Harry Potter idea, cashed the cheque from WB then abandoned the game entirely. Joke of a company.
WB is going to try to fix the sync at 10 PM PST on Monday January 11. See HPWULOLA's comment.
I believe this will correct our Wayspot syncing issue. We will be keeping a close eye on things, please keep me updated on how your maps look!
This will not be relevant in the future as this game will stop existing.
This issue was resolved exactly a year ago.