Googleカレンダーの同期: the setup order that holds up

Connecting a Google account to a calendar application on the Mac takes about two minutes. Getting it into a state worth relying on takes considerably longer, and most of that time is spent undoing. Events appear twice. Notifications fire from three places for the same meeting. The one shared calendar that prompted the whole exercise never shows up, so the account gets removed and added again, which changes nothing.

None of that is caused by doing the steps in the wrong order. It is caused by connecting before deciding anything. The setup screens ask technical questions and answer none of the ones that actually matter, so the decisions get made by default and then discovered later as symptoms. What follows puts the decisions first.

Decide three things before connecting

Which account is the default destination. Anyone with separate work and personal Google accounts has to answer "where does this go" every time an event is created. Left unanswered, that question gets re-litigated several times a day and eventually events start landing wherever the cursor happened to be. Picking one account as the default, and treating the other as the exception, removes the decision from daily use.

What comes down to the Mac. A Google account typically contains personal calendars, calendars shared by other people, subscribed feeds, holidays and birthdays. Pulling all of it into one view produces a day so crowded that personal commitments disappear into it. The useful split is between calendars checked several times a week, which belong on the Mac, and calendars checked monthly, which can stay in the browser.

Where notifications fire. Straight after connecting, the default state is often that Google's own notification, the desktop application's notification, and the phone all announce the same meeting. Deciding in advance which one is the real one turns the cleanup into a single pass rather than a week of switching things off as they annoy.

None of the three is a technical question, which is exactly why the setup process does not ask them. They take a few minutes to answer and they determine whether the configuration survives.

Connect one account, completely

Apple's Calendar adds a Google account from Settings, Accounts, then the add button, then Google. A browser window opens for the Google sign-in, because the protocol behind the connection refuses anything other than OAuth 2.0 and will not accept a password typed into an application field.

Before that, check delegation. Apple Calendar has a delegation feature for viewing another person's calendar on their behalf, and Google states that switching it off is what allows Google sync to work. Anyone who previously used delegation to see a shared calendar needs to clear it first, from Settings, Accounts, Delegation. Doing this before connecting avoids a puzzling first hour.

Then finish this account before starting the next one. Settings are held per account: the refresh interval, the list of calendars selected for sync, and the notification behaviour all belong to one connection and are not inherited by the next. Connecting three accounts and then trying to configure them produces a state where it is genuinely hard to remember which setting belongs where.

Choose what gets pulled down

Only calendars under My calendars, plus birthdays, sync automatically. Shared calendars and subscribed feeds live under Other calendars and stay behind until each one is switched on individually, on Google's sync settings page, and saved. After saving, refreshing calendars on the Mac brings them in.

This is the step that gets skipped, and skipping it produces the single most common false diagnosis in the whole process. The shared team calendar does not appear, the conclusion is that sync failed, the account is removed and re-added, and the result is identical because the account was never at fault.

Choose by how often a calendar is actually opened. Everything pulled down adds another colour to the day, and past a certain density nothing stands out. Adding a calendar later takes seconds, so starting narrow costs nothing and starting wide costs a cleanup.

There is a second route for calendars that only need watching. Each one publishes an address in iCal format that can be pasted into the application as a subscription, which is read-only. Useful for a roster or a public schedule. The rule is to pick one route per calendar: connecting the account and subscribing to a calendar inside it produces two copies of every event in it.

Set the refresh interval, but set it last

On Apple Calendar, each account has a Refresh Calendars menu under Settings, Accounts. Where the server supports it, push is available, and Apple describes it as the account updating itself automatically when a change is made on another device using the same account or when someone edits a shared calendar on it. Where it is not offered, the choice is a time interval.

The reason this comes last is that shortening the interval fixes nothing that was caused by delegation or by an unselected calendar. Changing it first produces no visible improvement, which invites further changes stacked on a setting that was never the problem. Check delegation, check the sync selection, then set the interval.

Subscribed calendars carry their own interval, separate from the account. Control-click the calendar name, choose Get Info, and pick from the Auto-refresh menu. Since these are one-way feeds from someone else, a long interval is usually correct. A holiday calendar checked every five minutes is pure overhead.

Add the second account the same way

Repeat the whole sequence for each additional account: delegation, calendar selection, refresh interval, notifications. Nothing carries over.

Skipping the repeat produces a specific and misleading symptom. Some events update promptly, others lag, in the same window on the same machine, which reads as an unreliable connection. It is a half-finished configuration, and the half that is finished is whichever account happened to be selected when the settings were changed.

Assign colours per account at this point as well. The reason for keeping work and personal separate is to treat them differently, and that only works if the difference is visible at a glance rather than requiring each event to be opened.

Work and school accounts sit under an administrator, who sets a ceiling on external sharing that no individual setting can exceed. When event details come through as busy blocks with no titles, the local configuration is not the place to look. Google notes the same thing from the other direction: if a calendar's private address cannot be found, an administrator may have changed the sharing settings for the organisation.

Invitations follow the address they were sent to, which is worth stating explicitly because it catches people who consolidate mail but not calendars. A meeting invitation arriving in a unified inbox does not place the event on the Mac unless the account that received it is one of the connected ones. The result is a meeting that is visible in mail, absent from the grid, and therefore missed. Anyone who still receives work invitations at an address that is not connected should either connect it or stop using it for scheduling.

Decide what to do with the browser

Setting up sync does not remove Google Calendar from the workflow, and pretending otherwise creates its own friction. Some things only exist there, so it is better to name them once than to hunt for a local equivalent every time.

Creating a new calendar is one. The protocol behind the connection includes a method for creating calendar collections and Google's interface does not implement it, so a desktop client cannot make a Google calendar regardless of how it is configured. Room and equipment booking is another, being a Google-specific system rather than part of the shared standard. Tasks are a third, since the format defines a to-do type that the interface does not serve.

Treat these as browser jobs and the desktop application becomes the place where the day is read and events are entered, which is what it is good at. Trying to make one surface do everything is what produces the endless search through settings panels for a feature that was never going to be there.

Clear the overlaps

Most of the work after connecting is removing duplication rather than adding anything. Three overlaps account for nearly all of it.

The first is two routes to one calendar, which shows up as every event having two boxes. Visible immediately, easy to fix, and covered above.

The second is the same commitment entered in two accounts. This one is a habit rather than a setting. Someone puts a client meeting in the work calendar so colleagues can see it and in the personal calendar so it appears at home, and then has to remember to change both whenever the time moves. The durable fix is to share the calendar rather than to copy the event.

The third is notification overlap, and it is the slowest to notice because it is an audio problem rather than a visual one. Google Calendar sends its own notifications, the desktop application sends notifications for the same events, and the phone does too. Nobody investigates this until the third alert for a single meeting. Returning to the decision made before connecting, switch off everything that is not the chosen source.

Time zones belong in this pass as well. Google Calendar has a primary time zone setting of its own, and macOS has a system time zone, and the two can disagree after travel or after a manual change. The symptom is events that look an hour or several hours off. Opening one event from next week and confirming the time straight after setup takes seconds and catches it before a meeting is missed.

Verify before relying on it

Create an event in Google Calendar in a browser, refresh on the Mac, confirm it arrives. Then change its time on the Mac, reload the browser, confirm the change went back. Both directions working is the whole test.

If only one direction works, the connection is a subscription rather than an account, and no setting converts one into the other.

Expect the first sync to be slow. The client takes everything once, then switches to fetching only what changed, so a calendar with years of history looks incomplete for the first few minutes. Rebuilding the connection at that point restarts the download from zero.

Finally, note what will never arrive, so the search for a setting does not continue indefinitely. Google lists email notifications for events, creating a new Google calendar, and room booking as unavailable in Apple Calendar. Deciding that new calendars get created in the browser closes that question permanently. The scope of what a desktop client can reach is set out under Features.

What to change first

Answer the three questions before touching any settings, then connect one account and finish it before adding another. Once both directions verify, the remaining friction is not in the connection but in how many steps an event takes to enter and whether travel between meetings has any shape on the grid, which is what Caltimate is organised around.