arnoldthebat
Unable to login in Google account on set-up
When I try to set up a personal account on the latest build it give a "something went wrong there, please try again" when logging into my Google account, when trying to create a new account it freezes at the terms and conditions page.
I am having the exact same problem here. tried 2 different google accounts and creating a new account. same problem on the last 2 daily builds and the last 2 special builds. Not sure what to try next.
I installed v85 as v87 seems to have this issue and it works, considering that I need chromium os for business computers I need the corporate enrollment but I can't do much without being able to go through the setup. Edit: This is on special builds, by the way, these are supposed to have Drive included in the files app right? Because that's not showing up, might be something I messed up or it just isn't a feature(?).
Hmm - let me have a look over the next few days (crazy busy in other stuff at the mo). I dint see any of that on my testing so its slightly worrying.
Hmm - let me have a look over the next few days (crazy busy in other stuff at the mo). I dint see any of that on my testing so its slightly worrying.
Thank you so much! Such an amazing work by the way! I'm not sure if the Google drive thing is normal as I still have the option to disconnect drive but it's never really implemented (v85 for arm64)
Sadly Google Drive integration is broken. Google close sourced it several months ago.
Oh ok got it, would have been somewhat practical but I mostly just use a windowed shortcut of Drive.
~~I can confirm that this is also happening on R80-special.~~ I've tried R87, R85 ~~and R80~~ (all special) and they all do this same thing with the initial sign-in. Guest mode works, though. Sadly, I can't use the vanilla versions on my desired hardware, so I can't try those.
Edit: R80 works after a second try. I think I just had a bad flash on my first try
It appears we aren't the only ones:
https://groups.google.com/a/chromium.org/g/chromium-os-discuss/c/57gNEvwx1m0
I have an R89 version in the works which still works so it appears Google have been tinkering
So, chromiumos builds may have reached an API limit on logins? This explains why my daughter was unable to log into her chromebook (running chromiumos as its an old now unsupported acer c7) ... which is a shame.
Please test with: https://arnoldthebat.co.uk/wordpress/2021/02/10/chromiumos-enhanced-builds-r89-13729-b/
Please test with: https://arnoldthebat.co.uk/wordpress/2021/02/10/chromiumos-enhanced-builds-r89-13729-b/
I'll try this tomorrow, hopefully, it works! I'll let you know.
It seems to work, however, there is no enrollment option, and also the setup options is a bit different, is this supposed to be version 89? In the menu, it says version 85.
Likely just a typo on my part. Ill have a look in day or so. Re Enrollment, thats going to disappear soon anyway from my builds unless you pop your own keys in as per https://arnoldthebat.co.uk/wordpress/2021/02/10/important-update/
Maybe you should add your accout to this group:
https://groups.google.com/a/chromium.org/g/google-browser-signin-testaccounts
About:
https://www.chromium.org/developers/how-tos/api-keys
In this document, google say:
In order to sign in to Chromium builds, please add your test account to [email protected] (accounts in this group are allowed to get access tokens bypassing the restriction above).
I am having the same problem with this build Camd64OS_R91-13904.B-Special Done all steps in https://arnoldthebat.co.uk/wordpress/2021/02/10/important-update Subscribed to both chromium-dev and browser-sigin-testaccount.
Please help. Thank you very much.
Did you enable Sync-api? Follow link and enable API
https://console.cloud.google.com/apis/api/chromesync.googleapis.com
There is no Sync-API.
Please be considerate. I am not a ChromiumOS veteran. I need more information to be able to make this work.
On Fri, Jan 21, 2022 at 3:37 AM sophiableich @.***> wrote:
Did you enable Sync-api? Follow link and enable API
https://console.cloud.google.com/apis/api/chromesync.googleapis.com
— Reply to this email directly, view it on GitHub https://github.com/arnoldthebat/chromiumos/issues/343#issuecomment-1018429368, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUI6SYLBI6RX3NGLMLSEX3UXFAPVANCNFSM4W3GKGXA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
Ah. I was not subscribed to chromium-dev.
On Fri, Jan 21, 2022 at 2:11 PM Coburn Ingram @.***> wrote:
There is no Sync-API.
Please be considerate. I am not a ChromiumOS veteran. I need more information to be able to make this work.
On Fri, Jan 21, 2022 at 3:37 AM sophiableich @.***> wrote:
Did you enable Sync-api? Follow link and enable API
https://console.cloud.google.com/apis/api/chromesync.googleapis.com
— Reply to this email directly, view it on GitHub https://github.com/arnoldthebat/chromiumos/issues/343#issuecomment-1018429368, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUI6SYLBI6RX3NGLMLSEX3UXFAPVANCNFSM4W3GKGXA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
Having the same issue. However I couldn't enable Sync API before (even though I was part of chromium-os-dev group) until getting there by direct link. However it still doesn't let me in. Tho, I've enabled it just now, it might be not refreshed yet
Can anyone confirm it works?
Upd: it works. Apparently .goggleapikeys has to be in different format than what docs specify. Example below for those who might have troubles in future.
'api': 'api_key'
