Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

locations with geo information are not supported by this account on Mac calendar

Just started today on Dec 29th 2022. It was working. When adding an event in the Mac calendar it errors and any details already put in are lost. It may be associated with my Google calendar where it may be trying to save info.

6 replies

Try System Settings/Internet Accounts and click on the account in question. If it asks you to log in, do so and that should fix the issue.

I ran into the same symptom on my new MacBook Pro, the morning after migrating from my old machine. I identified my root cause as google calendar needing to be reauthenticated. After I re-entered my google credentials, the issue went away.


Hope this is 00004000 helpful for anyone. Terribly useless error message, but that's life I suppose :p

further info. It is associated with the calendar which it is connected to. When connected to my google calendar it fails. When connected to my icloud calendar it works. When you switch to google calendar it deletes the entry all together which is the most annoying aspect.

I just updated to Ventura 13.3.1 and getting same error message


We're having the same issue as well for a calendar that is stored locally "On my Mac." When attempting to modify the "add location" area with an address, we get a pop-up. The pop-up states "Calendar was unable to save changes to event." Underneath that is another massage stating "locations with geo information are not supported by this account." After selecting okay, not only does the message clears but the event disappears off the calendar as well. This is a calendar that is just stored locally On the Mac (in a group of other calendars). Never had this issue until upgrading to Ventura today. Really should have waited for .3's release.


Has anyone located a fix for this?


Hi JPLeB, thank you for being kind and desiring to help. Unfortunately, the suggestion offered does not work on this issue, and the initial problem still persists.