#Chrome not staying signed in full

#Chrome not staying signed in full

If you are unwilling to switch to the full Google Chrome browser, then you are out of luck - there's literally nothing that the world or community at large can do on this. The section I put here in bold (the emphasis is mine) is the only course of action you have available to you if you want to use the Google profile sync still - stop using Chromium and instead switch to Google Chrome which does have access to the profile sync API bits at Google, and in turn will do Profile Sync. Will need to move on to using the official chrome package distributedīy Google, instead of chromium (which is probably what Google wants, I suppose that users that can't do without the profile sync feature

The official announcement states that starting March 15 In the stable channel wouldn't help, because it's not a version Packaging perspective to mitigate this regression. I'm afraid (and sorry) there's nothing that can be done from a Locally will continue to be available locally.Īnd once again, the developer makes a statement: That they won't be able to log into their Google Accounts in thoseįor users who accessed Google features (like Chrome Sync) through aģrd-party Chromium-based browser, their data will continue to beĪvailable in their Google Account, and data that they have stored Assuming there is a real (privacy) reason to be logged into the site, you should always log out of anyone you don't want to access that site might use the same browser af. Users of products that are incorrectly using these APIs will notice Answer (1 of 4): Generally speaking, the threat in these cases is someone else accessing that same site from the same browser.

This is an unfortunate consequence of a decision by Google to restrict access to the sync API to Chrome only (which explains why in comment #3 you're seeing that chrome 89 on linux works fine).Īnd the quote by the Ubuntu Developer from the Chromium upstream site data: SOLUTION: Google Chrome process will not close Chrome will not re-open Posted on Jby Steve Schardein A frustrating issue that I have encountered on multiple recent customers’ PCs is an inability to completely close all Google Chrome processesand, even more frustratingly, a consequent inability to reopen Chrome once it has. This is stated perfectly in the comment you linked to in that 'bug' (all 'bold' emphasis is mine): Their announcement on that change even said March was the date that this would get yanked, and March 15 would get actual login failure cases. Google made the decision that their profile sync APIs are going to be restricted to Google Chrome only, and it's a decision by Google, not by Chromium or users of Chromium, that we can't alter. You will need to use the actual Google Chrome browser if you still want profile sync to work. I really cannot stand it anymore and it's not usable for me.There's literally nothing that can be done by users or anyone other than Google to change this. It's a company's business e-mail and I'm using only one account. Message: AADSTS50061: Unable to complete signout. Sorry, but we’re having trouble signing you in.ĪADSTS50061: Unable to complete signout.

Some other times it's redirected to the error page on the unexpected out-of-blue signout event: Simply click on the person and sign into your google account and it will keep you signed in between reboots. In the top right corner, where the minimize button is (on windows), you will see a picture of a person.

It's a good idea to close all browser windows. If you use Google Chrome, you can sign into Chrome Browser. Every certain period of time I got logged out from Outlook Web App, part of Office 365, automatically like every hour without any apparent reason, and the message reads: