Pokémon Go’s latest update breaks Go Plus functionality: Player reports, workarounds, and what Niantic needs to fix
The Problem: What’s Broken in Update 0.331.0
Pokémon Go’s 0.331.0 update has introduced a critical bug affecting the Go Plus family of accessories, fundamentally breaking their core functionality for many trainers. This September 16 release was intended to deliver bug fixes and performance improvements, but instead created a new set of problems that undermine the game’s accessory ecosystem.
The primary failure mode involves Go Plus devices disconnecting within approximately one minute whenever the Pokémon Go application loses focus or the device screen locks. This renders the auto-catching functionality essentially useless for players who multitask or need to conserve battery life during extended play sessions.
Niantic’s development team deployed this update with standard release notes promising enhanced stability, but the reality for many users has been the opposite. The disconnect issue appears to be tied to how the game manages background processes in the latest version, potentially related to battery optimization or permission changes in the underlying code.
What makes this particularly problematic is the device’s designed purpose: Go Plus accessories exist specifically to allow trainers to play passively while focusing on other tasks. The current bug defeats this core value proposition, forcing players to keep their phone screen active and the app foregrounded—conditions that drain battery rapidly and prevent productive multitasking.
Player Experiences and Community Response
The Pokémon Go community has responded with detailed reports across multiple platforms, documenting the scope and severity of the issue. On TheSilphRoad subreddit, one trainer meticulously documented their troubleshooting journey, trying everything from device resets to complete app reinstalls without success.
“As soon as you switch to another app or lock your phone, the connection drops within 60 seconds,” reported a trainer on Pokémon Go Hub. “Reopening Pokémon Go immediately restores functionality, but this defeats the entire purpose of having an auto-catcher. It’s become a $35 paperweight until Niantic fixes this.”
Community frustration has been amplified by the forced nature of the update. Initially, some players found temporary relief by reverting to version 0.329.2, but Niantic quickly made 0.331.0 mandatory, removing this workaround option. The subsequent 0.331.1 update on September 19 failed to address the Go Plus issues, suggesting the development team may not have identified the root cause.
Social media platforms like Twitter/X have seen numerous complaints over several days, with trainers noting that their devices “basically make it useless until it’s fixed.” The problem appears to affect multiple device models, with users confirming that “it’s the same case with Go Plus+ also,” indicating this isn’t limited to a single hardware revision.
Interestingly, not all trainers are experiencing issues. Some community members report their auto-catchers continue functioning normally post-update, suggesting either device variability, operating system differences, or potentially inconsistent bug manifestation. This inconsistency makes troubleshooting particularly challenging and complicates community efforts to identify reliable workarounds.
Niantic’s Response and Update Status
As of current reporting, Niantic has not officially acknowledged the Go Plus connectivity issues stemming from update 0.331.0. The company’s communication strategy typically involves addressing widespread bugs through subsequent patches rather than immediate public statements, leaving trainers in limbo regarding resolution timelines.
The mandatory update enforcement represents standard procedure for Niantic when pushing critical updates, but in this case it has trapped affected players without functional accessories. This approach ensures all players are on the same version for event compatibility and anti-cheat consistency, but it eliminates individual workaround options during buggy releases.
Patch 0.331.1’s failure to address the issue suggests either insufficient bug reports reaching Niantic’s quality assurance team or technical complexity requiring more development time. Pokémon Go’s update cycle typically delivers fixes within 1-2 weeks for critical issues, though accessory-specific problems sometimes receive lower priority than game-breaking bugs affecting all players.
Trainers monitoring official channels should watch for updates through the Pokémon Go Live website, Niantic’s support Twitter/X account, and in-app news notifications. Historical patterns suggest that once acknowledged, such issues receive fixes within the next major or minor update, though temporary workarounds are rarely provided during the interim period.
Practical Solutions and Temporary Fixes
While no perfect solution exists until Niantic releases a proper fix, trainers can attempt several strategies to mitigate the issue. First, ensure your Pokémon Go app has all necessary permissions enabled, particularly background data access and battery optimization exemptions. On Android, navigate to Settings > Apps > Pokémon Go > Battery > Unrestricted. On iOS, check Background App Refresh in Settings.
Second, experiment with connection sequences. Some trainers report slightly longer connectivity by: 1) opening Pokémon Go, 2) connecting the Go Plus device, 3) waiting 30 seconds before backgrounding the app. Avoid locking the screen during this initial connection period, as this seems to trigger immediate disconnection in the buggy state.
Third, consider adjusting your play patterns temporarily. If you must use the Go Plus, plan sessions where you can keep your phone screen active but dimmed. Use battery saver mode within Pokémon Go (found in Settings > Battery Saver) to reduce screen brightness while maintaining foreground operation.
What definitely doesn’t work: Multiple trainers have confirmed that device resets, app reinstalls, cache clearing, and operating system updates fail to resolve the core issue. These methods consume significant time without providing relief, so prioritize the strategies above instead.
For trainers experiencing complete device failure, document your issue through Niantic’s official support channels with specific details: device model, phone operating system version, exact disconnection timing, and steps already attempted. While individual reports may not yield immediate fixes, they contribute to issue prioritization within Niantic’s development pipeline.
Broader Implications for Pokémon Go Players
This incident highlights broader concerns about Pokémon Go’s accessory ecosystem reliability. Auto-catching devices represent significant investments for dedicated trainers, and update-induced failures undermine confidence in both the hardware and Niantic’s quality assurance processes. Players should consider future update strategies, potentially delaying non-mandatory updates during critical gameplay periods.
Community monitoring becomes essential during such periods. Follow reputable Pokémon Go news sources like Pokémon Go Hub and monitor TheSilphRoad subreddit’s technical support threads before applying updates. The community often identifies issues within hours of release, providing early warning that might allow you to delay updating until a fix is confirmed.
Long-term, this situation may influence how trainers approach accessory purchases. While Go Plus devices offer convenience, their dependency on game updates creates vulnerability. Some veteran players maintain secondary catching methods (like quick-catch techniques) as backups for when hardware fails due to software issues.
Pokemon Go’s level rebalance update accidentally blocks players from collecting items
Pokemon Go is quietly ending support for some Android devices
How to play Pokemon Go in 2025 – The ultimate beginner’s guide
No reproduction without permission：Game Guides Online » Pokemon Go update 0.331.0 squashes bugs but breaks Go Plus devices Pokémon Go's latest update breaks Go Plus functionality: Player reports, workarounds, and what Niantic needs to fix