Pokémon Go resumes random bans to users, be careful

    Pokémon Go resumes random bans to users, be careful

    Just like last summer due to an annoying bug, some users of Pokémon Go they found a ban on your account without any valid reason, despite having followed the rules of the game. This problem seems to have returned and is particularly affecting users Apple, which once you open Pokémon Go on your own iPhone they found the annoying ban message.



    It also seems that this time it is not a single admonition, which does not allow you to play Pokémon Go for a limited time, but of a series of continuous bans that keep appearing on the phone without users being able to play, particularly aggravating the situation. It seems that for the moment the only possible advice is that of do not open the application on iPhone, waiting for a correct fix first.

    According to the first statements of the community, it seems that the support of Niantic is not currently managing the situation correctly, perhaps due to the bug that caught them off guard, perhaps due to an excessive amount of requests from all over the world.

    We therefore await a resolution, obviously hoping that the Pokémon Go bans on the iPhone will be removed from the accounts of innocent users, and that they can return to play safely without having to pay unjust penalties. In fact, we just have toexpect an official update from the developer, who will certainly be able to clarify the situation over the next few hours, explaining the causes of the problem and providing a resolution for it.


    Before leaving you, we take the opportunity to refer you to our article about it another Pokémon Go bug, which for the moment has forced the software house to remove Team Go Rocket from the game, you can access it through this link. Have you already heard of the new community day that sees the Pokémon Snivy as the protagonist? Find our in-depth analysis in the following article.


    add a comment of Pokémon Go resumes random bans to users, be careful
    Comment sent successfully! We will review it in the next few hours.

    End of content

    No more pages to load