nextcloud
Event with invitation and shared calendar ...
Steps to reproduce
1.as USER X, create en event and invite USER Y and Z from your NextCloud Instance
-
User Y Refuse the event and User Z accept the Event
-
If User Z share his calendar with User Y, in the NextCloud Calendar, the refuse event by Y will be shown as refused in the calendar App when showing the user Z Calendar ...
-
When Sync into macOS Calendar App for User Y that want to see the calendat of User Z, the event won't show at all...
Expected behavior
The Event from the shared calendar to another user should appear as when we consult other user calendar we want to wee what he have into his agenda...
Actual behavior
The event does'nt show
Calendar app version
5.5.7
CalDAV-clients used
No response
Browser
No response
Client operating system
No response
Server operating system
No response
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
No response
Updated from an older installed version or fresh install
None
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info
No response
No error ...
The problem is not an error... Into the NextCloud Calendar Web App, the Event From the other user is marked as "You refuse this event" ... But that status don't seem compatible with macOS calendar ...
When i take a look to the Event of another user that share his calendar with me, i should see that he have accept the event, not that i refuse to join it ... So i think it's more the way the current NextCloud Calendar Drive those attendee that is incorrect !
So the attendee status is handled by the RFC PARTSTAT property in the event, We use a RFC defined DECLINED, so if the macOS is not reading this properly there is not much we can do about it.
You can post the event and I can check if it is set correctly.
The decline in my calendar is fine!
But the decline into the calendar of the user who share his calendar with me and that he accept the event is not good !
I am also facing this very annoying issue. The only way of solving it is to use the web UI: most of the end users won't even have the idea to do it.
