4 ms·
I feel the title editorializes a bit too much. The thread only confirms the bug, not a specific cause yet. As sibling comments indicate, the effect on GrapheneO
by kjander79 1mo ago
I feel the title editorializes a bit too much. The thread only confirms the bug, not a specific cause yet. As sibling comments indicate, the effect on GrapheneOS users is undetermined.
- aniviacat 1mo agoFor me, the issue also only occurs sometimes. Usually I can download apps like normal.
- g-b-r 1mo agoEven in the last days? If you use anonymous accounts it seems to affect everyone, when it works it only works for a few downloads
- titularcomment 1mo agoThis is standart, and happens constantly with Invidious (youtube frontend). This happened before on AuroraOSS too. They probably just flagged the accounts and no API change or A/B testing an API change.
- kevincox 1mo agoThis also has nothing to do with GrapheneOS except for some user overlap.
- tentacleuno 1mo agoIf anything, it seems more poised to damage the usability of systems which actively rely on Aurora Store, like CalyxOS and the likes. Graphene actively discourages using Aurora.
- archon810 22d agoYeah, this seems to have nothing to do with GrapheneOS. There's some account used by default when you don't use your own in Aurora, and Google has started seeing too much traffic to the Play Store APIs from it. I'm surprised it took this long tbh. The server busy errors are transient and go away after a while, but if the load persists, they'll come back.