-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac Os Ventura: CalDav no longer allows "Add Invitee" #1431
Comments
Any idea what the reason for this could be? Are different capabilities necessary to bring it back or did Apple just lock down the feature ..... somehow? |
We have no idea.
… On Dec 8, 2022, at 11:56 AM, Thomas Müller ***@***.***> wrote:
Any idea what the reason for this could be? Are different capabilities necessary to bring it back or did Apple just lock down the feature ..... somehow?
—
Reply to this email directly, view it on GitHub <#1431 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHA6U2AFEMDFQSIKSUXRGLWMIHLVANCNFSM6AAAAAASYJQVSI>.
You are receiving this because you authored the thread.
|
LuxSci is looking to hire someone to address this issue (and then some others) in this package. DeepDiver1975 -- are you interested? We need to get this resolved soon. Here is a job post on UpWork (https://www.upwork.com/jobs/~01211754d54b5b8d08), but we do not need to use that platform. |
Do you think there is any way we could pay sabre.io to prioritize resolution of this (and related) issue? |
Users who have upgraded to Mac OS Ventura, already having working connections from Mac Calendar to sabre/io CalDav, suddenly can no longer add attendees to meetings.
When you create a new event in macOS calendars, you have the option to “Add Invitees” directly on the event. This appears to be missing from CalDAV when on macOS Ventura (13.x.x) but the field DOES still appear when adding calendar events with iCloud calendars.
This has been confirmed on many different Macs under different users in different companies.
The text was updated successfully, but these errors were encountered: