-
Notifications
You must be signed in to change notification settings - Fork 100
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
Trying to sign in on a Family Link account fails. #857
Comments
It seems as the browser User Agent or browser version is outdated. |
This line of text seems to be the user agent being defined. Maybe try switching the user agent to something new? |
User-Agent is irrelevant, even on a real android smartphone with android 9 you see this error on a restricted account. Tested over a half year ago, with an android webview. The first thing what worked for me was to use fake gapps login flows. |
The best thing is to use a regular account with this launcher. You are forced to enter the credentials of the regular account in both cases, the restricted account has a login barrier. |
Android 9 has Gapps support, and official documentation says that it should work for 5.1 and up. Is this due to bad design of the launcher's Webview? |
No, Google Login for that kind of account needs more than a android webview. It needs to be a special gapps webview for resticted accounts to pass the check. My regualar Google Account can sign in via Firefox and Chromium. Your account can't.
It worked for me, if you enter the login tokens into the manual login flow. That option only exists in qt6 versions of the launcher, e.g. AppImage bookworm and flatpak. Any reason why you need to login with a parental controlled account? The account registered as parent also need to sign in anyway or login is denied. |
I know that.
Use a real Web Browser for login. I know for sure you can log in onto web browser on family link
Okay. So that's the only working method. |
Describe the bug
When trying to sign in on a Family Link managed account it says that the device is incompatible.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should have just went to the parent verification screen.
Screenshots
Desktop:
Additional context
This seems to be a GApps problem or something like that. I don't know.
Yes, I have tried a "solution" but it doesn't seem to work.
The text was updated successfully, but these errors were encountered: