Here is where you can find a list of issues 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 related 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: July 28th, 2022

Pokémon caught with PGP/PBP does not count towards Daily Active Incense
Issue description: Pokémon attracted to Daily Adventure Incense caught using a PGP or PBP will not appear on the summary screen or count towards Special Research.
Issue status: Investigating

Candy is displayed as the same color on the Pokémon catch detail screen for all Pokémon.
Issue Description: After a successful catch encounter, the color of the candy on the popup is the same regardless of the Pokémon caught. This is purely a visual bug, the correct candy for the caught Pokémon will be added to your inventory.
Issue Status: Resolved in next release (0.243.2)

"Add {#} friends" task may not complete even after adding the required number friends.
Issue description: After adding friends to complete tasks such as "add 3 friends" to complete a Special Research task, the task is not marked as complete and Trainers are unable to progress in their Special Research.
Issue Status: Resolved

Some Pokémon appearing due to Lures and Incense are unable to be encountered
Issue description: Some Pokémon appearing due to a Lure or Incense will disappear immediately when tapped.
Issue status: Resolved

Trainers have recurring issues with Adventure Sync on iOS devices.
Issue description:
Trainers may experience issues enabling or disabling Adventure Sync, or may experience inaccurate distance tracking.
Issue status: Mitigated in release. Reinstalling your application and re-enabling all permissions in device and application settings may help resolve further issues.