-
-
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
Cannot login IEEE account #2206
Comments
Hi guys, if you see this comment and have Google accounts managed by a third party, could you please test signing in with microG and see if it works? |
microG does not support educational, institutional or corporate accounts if they require any sort of device management. This is a known issue. |
Is this out of scope for the microG framework, or can we expect support for it in the foreseeable future? |
It's not unlikely we'll see some level of support at some point. Worst case we might just pretend to the server to support device management, just so one can sign-in. |
Hi @Kruegerrr, I'm working on an implementation for accounts that require device management in #2296. Could you please tell me whether you are still experiencing the issue as you described as of today? The reason I'm asking is that there seems to have been some change not long ago where the login flow would seemingly complete like normal, but then the account would still be mostly dysfunctional. Is that perhaps also the case for you now? |
Hi @fynngodau, I tried login again and it failed just as before with the sorry message. |
Describe the bug
The following message is displayed when returning from IEEE login portal: "Sorry, there was a problem communicating with google servers when adding Google account".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Successful login
System
Android Version: 13
Custom ROM: LineageOS 20 For MicroG
Additional context
There is no problem signing in to a personal Google account on my system.
2FA is disabled for my IEEE account.
The text was updated successfully, but these errors were encountered: