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.
Frequent log in
Elijustrying-ING
Posts: 5,482 Ambassador
in Report a Bug
Possibly linked to the issue that occurred on Friday with numbers showing on profile.
Since that was fixed my profile when I open it just has name and nothing else, contributions are blank and I get told something major has happened.
logging out then in fixes it but for a short while.
Tagged:
Comments
Thanks for reaching out @Elijustrying-ING! If you haven't yet, please try to clear the browser cache & cookies and then login to check if the issue continues. Let us know how it goes!
I had the same issue yesterday (Monday 8/8 EDT). Switching between Profile and Contributions showed stale (cached?) data; I did not try to Review. Reloading Wayfarer page in Chrome took me to the login screen.
I don't know whether or not this issue has been resolved.
I assumed that the Wayfarer team was restarting the server to try to fix the L38 issue in Pokémon GO (https://community.wayfarer.nianticlabs.com/discussion/35209/new-wayspot-issue-in-pokemon-go/p1?new=1).
Edit: this issue seems to continue today too (Tuesday 8/9 EDT).
@NianticOtoStar
I’ve just done that so will see how it goes.
But now I am getting the default Cupids Span in my showcase.
@NianticOtoStar
That hasn’t worked.
cupids span has gone so that’s ok.
I was logged out while reviewing, and after refreshing had to log back in again.
My issue appears to have been resolved. No frequent logins as of yesterday or the day before.
Same here. Fixed