Google Calendar Alarm Not Syncing on iPhone? Fix It

Why does a Google Calendar alarm not sync on iPhone?

In most cases, the event is syncing fine — iOS just hasn't fetched it yet, or the calendar it lives on isn't checked. The fix almost never involves Google's servers; it involves a toggle on the phone that got switched off, a fetch schedule set to manual, or a secondary calendar that was never enabled for mobile in the first place.

Three settings cause the overwhelming majority of reports: the per-account Calendars toggle, the Fetch New Data schedule, and Background App Refresh. Google Calendar usually doesn't sync with an iPhone because Calendars is switched off for that account in Settings, Calendar, Accounts, or because iOS is set to sync only recent events. If you're using a third-party alarm app on top of the calendar, there's a fourth layer: whether that app has permission to read the calendar at all. That's the layer this guide spends the most time on, since a missed sync there means a missed alarm, not just a missing event on a screen you weren't looking at anyway.

Which iPhone setting actually controls Google Calendar sync?

The Calendars toggle under your Google account is the master switch — if it's off, nothing else matters. On iPhone: Settings, then Apps, then Calendar, then Calendar Accounts, tap the Google account and confirm Calendars is on.

If that toggle is already on, check the visibility layer next. In the Google Calendar app, open the menu and confirm the calendar has a tick beside it. In Apple's Calendar app, tap Calendars at the bottom and check the same. An unticked calendar behaves exactly like a broken sync — the events are there, they're just hidden from the list you're looking at.

Fetch and Background App Refresh handle timing, not visibility. Go to Settings, Apps, Mail, Mail Accounts, Fetch New Data. Make sure your Google account is set to Fetch, not Manual, and choose a frequency like every 15 minutes. Separately, check Background App Refresh under Settings, General, Background App Refresh, and make sure it is enabled for Calendar. With both set correctly, new events typically land within a few minutes instead of waiting for you to manually open the Calendar app. If you haven't walked through the full connection process recently, the guide to connect Google Calendar to iPhone alarms covers setup from scratch, which is sometimes faster than troubleshooting a half-broken old connection.

Why are secondary or shared Google calendars missing from the sync?

Because iOS only syncs your primary Google calendar by default — secondary and shared calendars need to be turned on separately, from a page you can't reach inside iOS Settings at all. Shared calendars and secondary calendars are not enabled by default on iOS. Visit calendar.google.com/calendar/syncselect in a browser, check every calendar you want on your iPhone, and save. After the next sync cycle, those calendars will appear in the Calendar app under your Google account.

This single setting explains most "my work calendar never shows up" and "I added my partner's calendar and nothing happened" reports. It also explains a related limit worth knowing about: iOS syncs a maximum of 25 Google Calendars per account, so if you have more, deselect calendars you rarely check. If you're juggling a work account, a personal account, and a few shared calendars, the guide on syncing multiple Google calendars on iPhone walks through managing all of them without hitting that ceiling, and work and personal calendars in one alarm list covers how Pealo handles the same accounts once they're synced correctly.

Why does a synced event still not trigger an alarm?

Because iOS Calendar notifications and real alarms are built on different technology — a synced event only produces a banner unless something is specifically configured to turn it into an alarm. Native Calendar alerts are local notifications, which iOS silences in Silent mode, Do Not Disturb, and most Focus modes. Apps built on Apple's AlarmKit framework, by contrast, ring like the Clock app regardless of those settings. The distinction matters more once sync is fixed, because a perfectly synced event that only sends a notification will still get missed.

Pealo reads the same Google Calendar account through the Google Calendar API, then converts each event into a real AlarmKit alarm instead of a notification. That means the sync problem and the "it didn't ring" problem need to be diagnosed separately — fixing one doesn't automatically fix the other. The table below breaks down what each layer is responsible for.

When should you remove and re-add the Google account?

Do it when the toggle, fetch settings, and syncselect page are all correct but events still don't appear — that combination usually points to a stuck authorization token rather than a hidden setting. On iPhone, account re-adding does the job that cache clearing often handles on Android, rebuilding the local connection without a direct "clear cache" button.

A changed Google password is a common trigger for this. If the issue is a changed Google password, go to iOS Settings, Calendar, Accounts, Gmail, and check if there's an error there with a prompt to re-login. Re-adding is straightforward: delete the account under Calendar Accounts, restart the phone, then add it back and sign in fresh. This also resets the sync range, so if you'd previously set a short history window, confirm it afterward. It's the same underlying account iOS uses for notifications, so if alerts have gone quiet since a password change or iOS update, the calendar alerts stopped after iOS update fix covers the overlap between those two problems.

Why doesn't a synced Google event show up in an alarm app?

Because the alarm app needs its own calendar permission, separate from whatever the Calendar app has. iOS asks for calendar access per app, so granting it to Apple's Calendar app doesn't automatically extend it to anything else reading from EventKit or the Google Calendar API.

Check Settings → Privacy & Security → Calendars, confirm the app has Full Access, and reopen the app to force a re-read of the account. If an event exists in Google Calendar and in the native Calendar app but not inside a third-party alarm tool, that permission screen is the first place to look, followed by whether the specific calendar is enabled inside that app's own settings — the same per-calendar checkbox problem that affects Apple's Calendar app. For a side-by-side look at how different alarm apps handle Google Calendar, iCloud, and Outlook accounts, the comparison of calendar alarm apps for 2026 breaks down permission models across nine options, and loud alarms for Google Calendar events covers what Pealo specifically needs to read an account correctly.