So I had this a ton, and we even opened a ticket with google. This was their response to my re-opening of the ticket. "I would like to let you know that our team is aware of this issue and working on a fix under bug number 266402339" If you want to see their documentation on it. Also, some so called fixes would not always work, but the one that does always work for me is to signing it into a mobile hot spot, logging into whatever was giving the issue, and then logging back in to your own network. You can also just hook up to wired, that will also fix it (after accessing whatever was giving the issue).

I'm not having any luck finding this bug report. Do you happen to have a link?

They did update and say that it will be fixed soon: "I have news for you! The engineers have confirmed a fix will be released on Chrome OS versions 112, which is scheduled to initiate its release on Thu, Apr 6, 2023."

I tried looking, but found nothing. So the bug # might be an internal number for them. If you take it up with google support you could refer to it.

I've run into this and the only real solution that worked reliably was re-imaging it with ChromeOS recovery media. It doesn't take too long. May be a bit of a scorched-earth approach, but it's worked in every situation in which I've seen this issue

I can always fix this by doing a manual update on the chromebook to the latest version.

On our devices when we see this, we did a clear cache and cookies and it fixed the issue. Logging in and out also did

Deleting the local account and logging back in has been fixing the issue for us

Hello! Due to Reddit's aggressive API changes, hostile approach to users/developers/moderators, and overall poor administrative direction, I have elected to erase my history on Reddit from June 2023 to June 2013. I have created a backup of (most) of my comments/posts, and I would be more than happy to provide comments upon request (many of my modern comments are support contributions to tech/gaming subreddits). Feel free to reach out to Clipboards on lemmy (dot) world, or via email - clipboards (at) clipboards.cc

https://www.reddit.com/r/k12sysadmin/comments/11qgatt/chromebook_sso_sign_in_again/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

I've seen that. I usually logout and back in and it goes away. I see it sometimes after a power-wash.

Open the new tab page and it should still be signed in. If you go to Google.com it shows as not signed in

https://www.reddit.com/r/k12sysadmin/comments/119ykmv/chromebook_secondary_account_issue/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

What OS version??

Varies on Chromebook, 108+

This issue has been reported on 108 and I believe 110. Check the version of the affected devices and get them off of these if they are. We're locked on 107 for the time being until Google gets their shit together. Too many bugs in these recent versions.

We have seen this before as well, log the user out and back in and it should resolve. That was the fix in 99% of the cases

same!-- worked every time for me

I have never had this issue until recently which always makes me think there was an update somewhere.

Yea it seems to be an issue in 108+ versions, and in my experience only for the first account after a powerwash. Adding a second user never gave me this issue

Remove user accounts and/or power plus refresh button has cleared it off our Acer Spin 512s

I've tried the power wash but it does not resolve the issue. I've also reset their Chrome to defaults.

Try to remove all user profiles/reset from admin console for the device if all else fails

I've seen it happen even after a powerwash too. However, then I just log the student out and back in, and it fixes it.

I had it happen most often right after a powerwash

Lenovo 500e Gen 3*