Here is a list of issues related to GO Battle League that are currently being investigated by our engineering team. This list will be updated regularly, and issues will be added and removed as they are discovered and resolved. Please note that this is not a comprehensive list of all issues we are aware of or working to fix. You can find the list of known issues unrelated to GO Battle League here.
To report a bug that isn’t listed here, or get one on one support, please submit a ticket in-app under the Settings menu, or see our article on how to best contact us for different issues.
Last updated: September 19, 2024
Battle notifications not displaying for some players
Issue Description: Certain in-battle notifications, such as "Super Effective" or "Defense fell", are not displaying during GO Battle League Battles and other Trainer Battles although the correct effect is taking place. This does not affect non-Trainer Battles such as Raid Battles, Gym Battles, etc.
Issue Status: Resolved
Sometimes the game may be less responsive as the final Pokémon faints.
Issue description: The final action of a battle can experience delays in certain situations.
Issue status: Resolved
Fast Attacks sometimes prevent Charge Attacks from working
Issue description: If a Trainer tries to use a Charge Attack at the same time as an opponent’s Fast Attack that will cause the currently battling Pokémon to faint, the Charge Attack may not work.
Issue status: Resolved
Fast Attacks that occur simultaneously and cause both Pokémon to faint may not result in a tie
Issue description: Fast attacks that will cause the match to result in a tie (both Pokémon fainting) will often not result in a tie.
Issue status: Resolved
Force Swaps sometimes cause the opposing Trainer to miss a turn.
Issue description: When a Trainer is forced to switch Pokémon due a fainted Pokémon, their opponent may experience a short delay.
Issue status: Resolved
Trainers sometimes experience an error in the matchmaking process but still begin the battle.
Issue description: When one Trainer experiences an error during the matchmaking process, the match starts anyway.
Issue status: Resolved
Trainers may briefly be taken to the battle screen during a canceled match.
Issue description: Sometimes when a match is canceled, Trainers will momentarily see their opponent in the Arena before they exit the Battle. This does not affect Trainer ratings and is purely a visual lag.
Issue status: Working on a fix
Issue description: The final action of a battle can experience delays in certain situations.
Issue status: Resolved
Fast Attacks sometimes prevent Charge Attacks from working
Issue description: If a Trainer tries to use a Charge Attack at the same time as an opponent’s Fast Attack that will cause the currently battling Pokémon to faint, the Charge Attack may not work.
Issue status: Resolved
Fast Attacks that occur simultaneously and cause both Pokémon to faint may not result in a tie
Issue description: Fast attacks that will cause the match to result in a tie (both Pokémon fainting) will often not result in a tie.
Issue status: Resolved
Force Swaps sometimes cause the opposing Trainer to miss a turn.
Issue description: When a Trainer is forced to switch Pokémon due a fainted Pokémon, their opponent may experience a short delay.
Issue status: Resolved
Trainers sometimes experience an error in the matchmaking process but still begin the battle.
Issue description: When one Trainer experiences an error during the matchmaking process, the match starts anyway.
Issue status: Resolved
Trainers may briefly be taken to the battle screen during a canceled match.
Issue description: Sometimes when a match is canceled, Trainers will momentarily see their opponent in the Arena before they exit the Battle. This does not affect Trainer ratings and is purely a visual lag.
Issue status: Working on a fix