Skip to content
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

Minimum requirements for Google Family Link #766

Open
yespah opened this issue Jan 25, 2023 · 10 comments
Open

Minimum requirements for Google Family Link #766

yespah opened this issue Jan 25, 2023 · 10 comments

Comments

@yespah
Copy link

yespah commented Jan 25, 2023

When I try to log in to Google Play Store with my daughters credentials, I'm met with "Update required"

Full message:

Update requried

To sign in with a Google Account managed with Family Link, this device needs newer software.

Minimum requirements

Android 5.1 & Google Play services 8.6

Recommended

Android 7.0 or higher

Learn more about devices at g.co/FamilyLinkFAQ

@ChristopherHX
Copy link
Member

The problem is this launcher does neither use Android or Google Play Services for the sign in process and therefore cannot be updated.

I guess you would also get the same error if you sign in with your webbrowser via https://accounts.google.com/EmbeddedSetup/identifier?flowName=EmbeddedSetupAndroid Source

@sschuberth
Copy link

and therefore cannot be updated.

So, is there any other way to make the launcher compatible with Google accounts managed by Google Family Link?

@ChristopherHX
Copy link
Member

ChristopherHX commented Feb 14, 2023

You can try to use this apk to sign in on the flatpak (manual sign in)

You will have to copy the two auth values from the android app into the flatpak to complete sign in.

It's very complex to sign in on such accounts

You need to open the settings app and search for microg then open it's settings and press add account

@radeeyate
Copy link

radeeyate commented Jan 28, 2024

You can try to use this apk to sign in on the flatpak (manual sign in)

Hey, it seems the build expired, so I can't get the APK. Would it be possible for you to run another build?

@ChristopherHX
Copy link
Member

@radeeyate I'm not trying to build it again no idea why sudo now throws an error. Found the ca 1 year old apk of the action run on my phone and reuploaded it as a release.

See https://github.com/ChristopherHX/PlayToken/releases/tag/2023.1

Play protect will guide you to not install it.

I doubt that someone not insisting to sign in with a restricted account want to go through all the hazzle.

Tested today and the credential are still displayed in the app.

@radeeyate
Copy link

Ah, thanks for that! Unfortunately, I don't have any other choice of account without family link.
I got the token needed, now where do I need to put it. I don't see any options in settings of the launcher, is there a file I need to put them in? (installed via apt)

@ChristopherHX
Copy link
Member

@radeeyate The manual login has only been recently backported to qt5 builds, so you currently have to switch to the nightly apt repo / get a nightly appimage to get access to manual login.

E.g. try to login via https://github.com/minecraft-linux/mcpelauncher-manifest/releases/download/nightly/Minecraft_Bedrock_Launcher-x86_64-v0.12.1.204.AppImage then sign in will be applied to the apt version.

You can leave the email field of manual login blank, it's no longer required to provide.

After sign in with that AppImage just delete it.

Those versions have a manual login button on the top of the webview.

@radeeyate
Copy link

Awesome, that worked! Thank you so much!

@thanone2
Copy link

how does one get these cookies from chromium?

@Niklas20114552
Copy link

The URL in the Manual Login has never worked for me. Everytime I try to log in with my google account it just says "Something went wrong" and - typical Google - without any further error information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants