-
Notifications
You must be signed in to change notification settings - Fork 352
Accounts and Authorization
Follow the steps below.

-
Minimize all Chrome windows and see if there is an authorization dialog lurking below all the windows. This is a Chrome issue where a dialog can lie underneath everything else and thus very easy to miss. Simply authorize it and you should be able to continue.
-
If there was no dialog in the step above, or if authorizing it did not change anything, Restart Chrome.
-
If that does not fix the authorization issue, then Sign Out of Chrome, and sign back in. Detailed instructions are available on the Chrome Support site. Several users have reported that this fixes the issue (which means this is a Chrome issue, not specific to this extension.)
-
If that fails too, Uninstall and Reinstall from the Chrome Web Store.
Google Calendar for Chrome 1.5+ uses the industry-standard OAuth protocol to fetch your calendar. Once authorized, it remembers that you granted permission, and will not request it every time you start Chrome. Google turned off version 2 of the Google Calendar Data API in November 2014, which had earlier made it possible to re-use your browser credentials. This is no longer permitted, and all apps at this point need to use OAuth-based authentication.
There are two ways: let’s assume your accounts are called Personal and Work. Personal account has two calendars, Personal-Main and Personal-Secondary. Work has two calendars, Work-Main & Work-Secondary.
-
Sign in to your
Workaccount in a browser, and share yourWork-Main&Work-Secondarycalendars with yourPersonalaccount (e.g. personal@gmail.com). Then sign in to Google Calendar for Chrome using yourPersonalaccount, and you will see all four calendars. -
Create a separate Chrome profile for each account,
PersonalandWork. You can then keep yourPersonalcalendars separate fromWork, but still access them in two different windows.Instructions on how to create a separate Chrome profile are available here.