TechNewsReel
Live

Aurora Store Anonymous Accounts Hit Widespread Installation Failures

Users of the open-source Play Store frontend report persistent errors that threaten app access for de-googled Android devices.

TechNewsReel Newsroom · September 1, 2026

Users of Aurora Store, an open-source frontend for the Google Play Store, are reporting a widespread failure when attempting to install applications using anonymous accounts. The disruption specifically impacts those who avoid Google accounts to maintain privacy.

According to reports on GitLab, the application returns a "&$Server busy, please try again later" error during the installation process. This failure has proven persistent, appearing even in the Nightly build dated August 31, 2026. Users have attempted several troubleshooting steps to bypass the error, including the use of VPNs, clearing application caches, refreshing anonymous accounts, and restarting their devices, but none of these methods have resolved the issue.

The Role of Aurora Store

Aurora Store serves as a critical bridge for the "de-googled" Android community, allowing users to download apps from the Google Play Store without requiring a Google account or the installation of Google Play Services. This functionality is essential for individuals using privacy-focused operating systems such as GrapheneOS and CalyxOS. These platforms are designed to remove Google's proprietary tracking frameworks to enhance user security and data sovereignty.

Implications for Privacy Users

If the ability to access the Play Store anonymously is permanently disabled, the consequences for the privacy-centric ecosystem are significant. Users of GrapheneOS and CalyxOS would be forced into a difficult compromise: create a Google account, thereby sacrificing the privacy goals of their operating system, or lose access to a vast library of essential Android applications. Such a shift would undermine the viability of maintaining a functional Android device without Google's ecosystem of tracking.

Current Status

While the community has noted the failure, it remains unconfirmed whether this is the result of an intentional block by Google or a general API failure affecting the anonymous account pool. For now, users of privacy-focused ROMs remain in a state of limbo as developers and the community investigate the root cause of the "Server busy" errors.

Sources

Get a notification when a big story breaks. A few a day at most — no spam.