Common Google sign-in errors

Coco signs you in through Google. When that handshake fails, it is almost always one of a few familiar issues. Work through these in order.

"Access blocked" or "app not verified"

During Google's verification process, or when you self-host your own Coco, Google may warn that the app is not yet verified. If you are running your own instance, this is expected — you are the developer of your own app. You can proceed through Google's "Advanced" option to continue. If you are unsure whether the instance is really yours, stop and check before continuing.

The wrong Google account

If you have several Google accounts signed in, the browser may hand Coco the wrong one. Coco then reads an inbox you did not mean to connect, or cannot find the mail you expect. Sign out of the other accounts, or use the account picker to choose the right one, and reconnect.

Permissions were not all granted

Google lets you uncheck individual permissions on the consent screen. If you decline the mail or calendar access, Coco cannot do its job and may error or come back empty. Reconnect and accept the full set — and if the broad wording gives you pause, read what Coco can do first so you know exactly what each one is for.

Expired or revoked access

Sign-ins do not last forever, and you may have revoked Coco's access from your Google account security settings. Either way the fix is the same: sign in again to refresh the connection.

Browser is blocking the popup or cookies

The sign-in flow uses a popup and cookies. A strict ad blocker, a blocked popup, or third-party cookies turned off can break it mid-flow. Allow the popup for Coco, or try again in a standard browser window before assuming something is broken.

Still stuck

If none of these clear it, note the exact error text Google shows and contact support — the wording tells us a lot. If sign-in works but the brief is empty afterward, see when the brief comes back empty.