-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MicroG Login Loop: "Account Already Exists" #1403
Comments
On top of this, now when I switch back and forth between apps and return to YouTube Vanced, it displays the "Add Account" popup every time So definitely worse off than before I tried adding an account to MicroG. |
Looks like the same problem as the one mentioned in #1373 . Please we need a fix. We can't even switch to another account from Google apps. |
@AinzTheSupremeOne I would say it might be related, but this is across the board, in the MicroG core settings also. It's not specifically a Vanced issue. |
The bug report #1373 describes a behavioir of stock apps, not of Vanced. |
Sure, but if you look at the issue you and @AinzTheSupremeOne referenced, it does not describe the bug which I expressed above. My YouTube loads, but I cannot login. MicroG acts like there is no account, even when I definitely entered one. It then tells me that my account already exists without actually logging in. |
In truth this bug prevents the login on every newer app (starting from January update). So yeah, is a general bug (what I meant). |
Fair enough, thanks for the clarification. I do hope this gets resolved soon! |
Ir happens the same with me. Even microg can't reconize that there is an account in my device, but the google ads works perfectly |
Is there something planned to try to fix the bug? because its since January. Is known how the bug can appear? |
Hey everyone so I think I might have fixed this issue. I simply uninstalled the GMSCore and GMSProxy apps and reinstalled them and now it works like a charm! |
Everything should already be fixed on the latest version of microG GmsCore so I close it for now. |
Which version is the fix? |
microG GmsCore 0.2.24.214816 |
Same problem here. I have the latest versions microg and YouTube vanced. |
The problem of "Account Already Exists" happens because the account really exist but it isn't usable, specially on non clean systems (so you won't see it inside Android accounts). The solution is delete these files (if they exist):
IMPORTANT: This will remove all accounts on the device (even non Google ones). After this you can add the account normally. |
I am experiencing this same issue, with the latest version of micro g. |
Here is the full list of files to delete (some devices have some files, while some other devices have other files):
|
I am on android 13 and can't seem to find any of those files. I have micro G on the work profile and logged in with work gmail. Everytime I am geeting the loop "account already exists" when it asks to login. |
The list is for various versions of Android so it is normal that you haven't all of them but you must have some. PS: If the problem happens only in work profile then it is probably a different issue. |
This continues for me. Latest version of CalyxOS, installed today. I'm slightly confused – is the proposed solution to delete the aforementioned files? That's no solution, surely. (Specifically, this occurs with com.google.android.apps.recorder) |
@RokeJulianLockhart |
Today I ran into the same issue after I logged out every devices for my Google account. Always getting "Account Already Exists" in MicroG. I tried cleaning data for the MicroG, reinstalling it, even using my cell phone number to log in. All failed. |
@tom282f3 |
Running latest Lineage OS for MicroG on my rooted OnePlus 6T. I cannot get past the add account screen even after properly authenticating. It acts as if I never added an account to MicroG. When I try again, I get the "this account already exists on your device."
I have searched through previous issues, even so far back as 2018 with no answers. Any assistance is appreciated. Thanks.
The text was updated successfully, but these errors were encountered: