Assigning to gogerald@ for further action, based on blame.

Hi Benoit, would you like to take a look?

I'll let Mihai take a look first since it's on Mac.

This looks like the refresh token for an account that was persisted on disk was somehow lost. It is very weird as this data is encrypted. Did you mess around with your profile data?

I don't remember doing anything weird. Is there a way to restore the token? Maybe then I can get back if the problem appears again.

Also, I found out that this also happens on Linux for me.

I would suggest you do the following:
1. Log the account id for which this happens (i'd like to see if the account id is an email or a Goia account ID):
    DCHECK(!refresh_token.empty()) << "Empty refresh token for " << account_id
2. Replace the DCHECK with "if(refresh_token.empty()) continue", which will simply ignore the empty accounts. Then sign out of Chrome (and then sign back in). Put back the DCHECK and let me know if you observe it again.

--Chrome Identity automated triaging--

This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I do not think I can do anything else for this bug - the DCHECK seems correct to me. I'm closing this bug as won't fix. Please let me know if it occurs again.