Play Store blocks AuroraStore, hurting GrapheneOS users
Privacy-focused Android users are facing roadblocks as Aurora Store, a third-party Google Play client, is increasingly failing to install apps anonymously. The "server busy" error suggests Google is actively hindering third-party access, impacting distributions like GrapheneOS that rely on such methods for app acquisition. This incident highlights the ongoing tension between platform control and user autonomy in the Android ecosystem.
The Lowdown
Aurora Store, a popular open-source client for accessing the Google Play Store without a Google account, is currently experiencing widespread issues. Users are reporting a persistent "Server busy, please try again later" error when attempting to download or update applications, particularly when using anonymous accounts. This problem is significantly affecting individuals who prioritize privacy and rely on operating systems like GrapheneOS or CalyxOS, which often recommend alternatives to direct Google Play services.
- The primary symptom is a recurring "&$Server busy, please try again later." error during app installation via Aurora Store, making it impossible to download new apps or update existing ones.
- This issue is consistently observed with anonymous accounts, suggesting a targeted action against Aurora Store's method of operation.
- Numerous troubleshooting steps, including using VPNs, clearing app cache and data, refreshing anonymous accounts, and reinstalling the app, have not provided a consistent or permanent solution.
- The problem is reported across various device models and Android versions, confirming it's not device-specific but rather an issue with Aurora Store's connection to Google's backend.
- Some users have noted intermittent success after multiple attempts or specific actions, but the overall experience remains unreliable.
- The error message itself is generic and provides no specific information about the underlying cause, further complicating user attempts to resolve the issue.
The consensus among users and developers points to Google actively blocking or rate-limiting the 'burner' accounts that Aurora Store utilizes for anonymous access to the Play Store. This move by Google puts a strain on privacy-conscious Android users who wish to maintain access to necessary applications without ceding extensive personal data to Google.
The Gossip
GrapheneOS & Aurora's Ambiguous Alliance
Commenters debated GrapheneOS's official stance on Aurora Store. While some asserted GrapheneOS recommends *against* Aurora in favor of the sandboxed Play Store, others explained they use Aurora specifically for its ability to install apps without directly logging into a Google account, aligning with their privacy goals. This highlights a user desire for privacy that sometimes diverges from strict project recommendations.
Google's Game: Blocking Burners
The overwhelming sentiment among HN users and the GitLab issue itself is that Google is deliberately blocking Aurora Store's access. The 'server busy' error is widely seen as an intentional obfuscation by Google to prevent third-party anonymous downloads. Users theorized that Google is flagging the pool of 'burner' accounts Aurora uses, or implementing IP-based restrictions, with some finding temporary relief by cycling through VPN server locations.
Workaround Woes & Inconsistent Installs
Users shared a litany of attempted workarounds, including clearing cache/data, refreshing anonymous accounts, reinstalling Aurora, and even using a personal Google account (though this defeats the purpose for many). The success of these methods was highly inconsistent, with some users reporting temporary fixes (e.g., one successful install before failure resumes) or 'hit-and-miss' experiences, underscoring the arbitrary nature of the blockage.