-2

Recently, I was playing Pokémon GO. It was fine, and there were no problems whatsoever until I spun a Pokéstop. It didn't come up with anything at all, apart from the error message "Try Again Later". I know that it is not a softban, since I am able to battle and train gyms, catch Pokémon, place them in gyms and collect my Pokécoins. Also, my Pokémon seem to be coming out of the gyms unnaturally often.

I am asking for a solution to this, and an explanation of why this is happening.

Yes, I did try again later, and I wasn't moving at the time.

This was on every Pokéstop I tried and it lasted more than 24 hours. Also, I was walking for some of it. I can spin it now, but every now and then, it almost gives a 24 hour ban!

By the way, I am also on iOS, which seems to be the place of most errors...

  • 2
    Did you try again later? What happened then? – Timmy Jim Apr 24 '17 at 2:19
  • 2
    Were you moving at all? – Vemonus Apr 24 '17 at 15:56
5

This is in most cases becaus of a problem with your connection with the servers. Try to check if your connection is okay.

2

As others have said, this tends to be because of a connection issue. One way to diagnose this problem is to look for the "spinning ball of death". In the upper right hand corner of the game you'll see a spinning white pokeball every time the game servers are being accessed. If you see it spinning frequently or non-stop some/all server interactions will fail. This can result in "failed to spin" pokestops, as well as other behaviors like "failed to start attack" on pokemon you can see but can't engage. Some things to try:

  • Try to fix your connection
    • Force quit the app and restart
    • Turn on airplane mode until your connection drops, then turn it back off
    • Disable WiFi
  • Attempt to spin a different Pokestop, then try again

Bear in mind that a failed Pokestop spin can sometimes still trigger the Pokestop cooldown (even when your connection is good). In these cases, it will take 5 minutes before you can spin the Pokestop again.

0

This has happened to me before and it's probably because of a bad connection with the servers that Niantic needs to fix.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.