iPhone and Mac calendar sync: nothing travels between them

The phrase carries an assumption that is not true. Two devices sound like they are talking to each other, and neither one is. The phone writes to an account. The computer reads from an account. When an event exists on one and not the other, the explanation is almost always that they are not looking at the same account, or that they are looking at different calendars inside the same account.

Getting that model right changes the order of troubleshooting completely. Without it, the first instinct is restarting, signing out, or deleting and re-adding the account, which is the slowest possible starting point and occasionally makes things worse. What follows works from where events are actually stored, through the two causes that account for most cases, and into the situations where the account itself behaves by different rules.

Events live in accounts, and some accounts never leave the device

Calendar events are not stored on a phone or a computer in any meaningful sense. They sit in iCloud, Google, or Exchange, and both devices act as windows onto that. When the arrangement is working, something created on one appears on the other in seconds to minutes.

Apple states the consequence plainly when describing where a calendar can be stored.

If you choose your iCloud account, the calendar is available on all your computers and devices that are set up with iCloud. If you choose On My Mac, the calendar is saved on your computer. Source: support.apple.com

The important word is the alternative. There is another destination, and it is not an account. On a Mac it appears as On My Mac, and on an iPhone as a calendar that lives only on that device. Events created there are working exactly as designed when they fail to appear anywhere else. Nothing is broken. A storage location was chosen that has no other end.

A second category behaves similarly for a different reason. Subscribed calendars, the kind holding public holidays or a sports fixture list, are read only. Attempting to add an event to one succeeds by silently putting it somewhere else, which is how an event ends up in a calendar nobody expected.

Before any other check, open the missing event on the device that has it and look at which calendar it belongs to. That single field resolves a large share of cases on its own.

How far each kind of calendar actually reaches

Sorting the possible homes for an event by how far each one travels turns a vague fault into a short list.

Where the event sits	Reaches the other device	Accepts edits	Shows attendee replies
iCloud account	Yes, on anything signed in to the same Apple Account	Yes	Yes
Google account	Yes, if that sub calendar is enabled on both	Yes	Yes
Main Exchange calendar	Yes	Yes	Yes
Extra calendar in an Exchange account	Yes	Yes	No
On My Mac, or a device only calendar	No	Yes	Not applicable
Subscribed calendar	Yes, as a read only copy	No	Not applicable

Two rows in that table produce the majority of reports. The device only row is the one that looks broken and is not, and the extra Exchange calendar row is the one that looks fine and is not. Everything else in the table behaves the way people expect, which is why the fault is worth locating in the table before touching any setting.

A detail hides in the subscribed row. A subscription has a storage location of its own, chosen when it is created. Put on iCloud, the subscription follows the person to every device. Put on the machine, the holiday list or fixture list appears on one computer and nowhere else, and it looks exactly like a sync failure while being a choice made months earlier in a dialog nobody remembers.

The default calendar splits a person's week in two

The second common cause is subtler, because everything genuinely is syncing.

Each device stores its own answer to the question of where new events go by default. If the phone defaults to a personal iCloud calendar and the computer defaults to a work Google calendar, then the destination of an event depends on which device was in hand when it was created. Both destinations sync correctly. Both are visible if looked for. Neither is where the person expected, which produces the impression of events vanishing and reappearing at random.

The symptom to recognise is a pattern rather than a one off. Events created on the phone consistently end up in one place, events created on the computer consistently in another. Once noticed, the fix is to set the same default on both devices and stop choosing per event. Choosing manually works fine on a calm afternoon and fails reliably when something is being entered while walking to a train.

A related case appears with Google accounts. Which of the secondary calendars inside a Google account are offered to the built in Calendar app is controlled in a browser settings page on Google's side, not on the device. A calendar excluded there will not appear no matter how many times the account is toggled on the phone. When most calendars sync and one specific one never does, that page is where to look.

Exchange accounts follow different rules

Work calendars administered through Exchange do not behave like personal ones, and the difference is documented rather than incidental.

Full calendar features are available only in your main Exchange calendar. Source: support.apple.com

Apple is specific about what is missing elsewhere. Additional calendars added to an Exchange account will not show updated invitations or attendee responses for their events. Those events are also invisible to delegates, meaning anyone sharing the calendar account, and they do not appear when someone checks availability.

The practical consequence is the opposite of what tidy minded people do. Splitting work events into separate Exchange calendars by project or client looks organised and quietly removes them from availability checks. Colleagues then see open time that is not open, and double bookings follow. Anything that involves invitations, responses, or being booked by other people belongs in the main Exchange calendar, and the tidying has to happen with colours or categories instead.

This also explains a class of complaint that gets reported as a sync failure. The events are present on both devices. What is missing is the response tracking, and no amount of re-authenticating will restore it.

How often each side goes looking

When the account and the calendar are both correct, the remaining variable is timing. Calendar on the Mac lets each account be set either to receive changes as they happen or to check on an interval, and a long interval is a perfectly ordinary reason for an event entered on the phone to take a while.

Two things are worth knowing rather than guessing. The refresh behaviour is configured per account in Calendar settings, so one account can be immediate while another is on a timer. And a manual refresh exists for the moment when waiting is not acceptable.

Choose View > Refresh Calendars Source: support.apple.com

Refresh behaviour also exists per subscription rather than per account. A subscribed calendar carries its own automatic refresh interval, set from Get Info on the calendar name, and an interval measured in weeks is a perfectly normal default for something like a holiday list. When one particular calendar is stale while everything else is current, that menu is the place to look rather than the account settings.

Only after visibility, defaults, and refresh have all been ruled out is authentication worth touching. Apple's published sequence for calendars that will not sync starts well before any account is removed: check the service status page for an outage, confirm the devices are on current versions of iOS, iPadOS, and macOS, confirm every device is signed in with the same Apple Account, confirm Calendars is switched on in the iCloud settings, and confirm the date and time settings are correct for the current location.

The last of those is the one people skip. A clock that has drifted, or a device left on a time zone from a trip three months ago, can cause the connection itself to be refused, and nothing about the symptom points at a clock. It presents as an account that will not authenticate, which sends people straight to deleting and re-adding it, which is the step most likely to remove local events that had never been uploaded in the first place.

There is an order to all of this, and it is worth following rather than improvising. Check which calendar the event is in. Check whether that calendar is ticked on the other device. Check what each device treats as its default. Check the refresh interval. Check the clock. Removing an account belongs at the end of that list, not the beginning, and by the time it is reached it is almost never necessary.

Two deliveries, not one failure

Seeing every event twice reads like the most severe kind of sync fault and is usually the mildest. Nothing failed. The same event arrived by two routes.

On an iPhone and Mac pair, the usual route is an account configured in two ways at once. A Google account added to the built in Calendar app while a second application also reads the same Google calendars produces two copies, distinguishable by colour. Being invited to a meeting and also creating a personal reminder of it produces two copies with different attendee information. Subscribing to a shared team calendar that already contains meetings the person was invited to produces two copies of exactly the ones that matter.

The correct response in every case is to remove one delivery route rather than to delete events. Deleting the visible duplicate often deletes the real invitation, which is how a sync annoyance turns into an apology.

What sync will not settle

Once both devices agree, a different set of problems becomes visible, and they get misreported as sync issues because that is the word already in use.

The first is that events entered on a phone and events entered on a computer are not the same quality. Something typed quickly on a phone platform tends to be a bare title. The same event entered at a keyboard picks up a location, attendees, and a meeting link. A calendar containing both kinds cannot be read reliably a week later, because half the entries do not say enough to act on. Making entry fast enough that the phone version is as complete as the desktop version is a bigger win than any sync setting, and the approach to that is set out in Entering events.

The second is travel. Events entered on the move and events entered at a desk sync perfectly and still produce an impossible day, because neither device compares where one commitment ends with where the next one starts. Two events fifteen minutes apart in different parts of a city are individually valid and jointly impossible, and nothing warns about it. Treating movement as an event with a real duration is covered in Travel time.

What to change first

Open the event that is missing and read which calendar it is in, then check that both devices default to the same one. Those two steps resolve most cases before any account is touched. If the events are all present and the day still does not hold together, the problem was never sync, and Caltimate is built for that second problem rather than the first.