It looks like you're new here. Sign in or register to get started.
Sign In with Ingress Sign In with Pokémon GO
I just looked at my profile and it's showing a 21-digit number where my name should be. It looks like it's just a cosmetic bug, and a little birdie told me they're aware of it already.
Same for me.
I was just going to ask if wayfarer has walked off in a sulk.
I’ve got the number thing. Also took several attempts to signin with Google as something major had happened.
Have got normal showcase.
Thank goodness its not just me, I thought I had gotten banned or something. Can't submit stops in PGO, even though I'm level 38.
Also I would refrain from posting the number anywhere. It may be a unique user ID so it's probably best not to disclose it.
Strange, mine is only 20 numbers. I wonder why you get an extra digit haha
I’ve got 21 too……your definitely missing out there@HankWolfman-PGO
Never mind, the number is apparently so long that the first digit is off the left hand side of my screen and can't be scrolled to. If I copy and paste it, the extra digit is included. Guess I am part of club 21 after all 😅
Happened to me as well.
@NianticGiffard can you provide some info?
I had it as well but logging off and on again helped.
I'm told and can confirm that it's been fixed. Log out and log back in.
I got the number and at first thought I'd either been 'tagged' onto a Niantic Watchlist or my account had been hacked. I, too, am relieved my name has now returned.
I think it still a bit unwell.
I keep having to log out and in again.
Thanks for reporting this, @Hosette-ING! Could you please clear the browser cache & cookies and then try to log in to check if that helps? Keep us in the loop!
@NianticOtoStar Thanks for the help but I'm way ahead of you. (-:
Before I posted this I reached out to a friend who, as I suspected, was the engineer who would deal with the issue. I posted because I expected other people would have the same problem and I wanted to let them know that Niantic knew about it. If you read my comment from later in the thread you'll see that the issue has already been fixed on the server side.