Strange behavior inviting people
After reading and commenting https://github.com/SimpleMobileTools/Simple-Calendar/issues/303 I figured out that some strange behavior occurs when inviting people.
Some background information I am using Nextcloud with DavX to sync contacts, calendar and tasks.
What I did:
- Created a new calendar entry.
- Started to add someone to the invite list and Got the request to allow access to contacts.
- Entered a name, the list got populated from the addressbook. I marked a name with email
- It showed up in the list of invited guests
- Saved the entry
- Logged into my Nextcloud Calendar app in my browser and found the entry but instead of an email I got just the name without spaces shown in the calendar app of Nextcloud.

- I went back to the calendar entry on my phone and looked at the entry added and figured out that the address book population misses spaces between first and lastname

- Tried to enter an email address directly into the field using the app, but it just does not work, everytime I enter it, and save the entry it gets removed automatically.
Seems that the App is not storing the data correctly to the entry, because if I just work with my webinterface of nextcloud this all works just fine.
I am using Version 6.6.1 Pro installed via Google Play Store
Got the same problem. Calendar entries with attendees created by Simple Calendar cause errors on my CalDAV server (Baikal) when syncing via DAVx5 and OutlookCalDavSynchronizer complains as well. Etar is working fine in this constellation.
Let me know if you need more technical details for debugging.
Same problem here. Newest SC Version and DavX. No invitation Mail will be send. Directly form the Nextcloud interface, invitation will be send.
Same issue. Using Davx5 to sync to Fastmail. When adding an event with no additional person invited, all works fine. When inviting, it breaks the event and doesn't properly trigger the invitation. Notably when swapping Google Calendar for Simple Calendar all works fine.
Maybe I have some information that can help: I also tried it with another calendar app and seeing this in the logs of DAVx5
04-03 23:14:37.125 9258 15294 D davx5 : ], attendees=[ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=TRUE;PARTSTAT=ACCEPTED:mailto:[email protected] 04-03 23:14:37.125 9258 15294 D davx5 : , ATTENDEE;CN=GivenName;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:[email protected]
While Simple Calendar produces this:
04-03 23:22:38.729 9258 15519 D davx5 : ], attendees=[ATTENDEE;CN=GivenName;CUTYPE=INDIVIDUAL;ROLE=NON-PARTICIPANT:mailto:[email protected]
So there is no RSVP=TRUE and the Role might be an issue. the organizer field seems right.
(Log is from Debug output of DAVx5)
Which is the reason invites are not sent, according to Davx5
Ill take a look at it later, thanks. Sadly there are so many things handled differently inside CalDAV. It isnt some protocol that just works the same way in all apps/services.
According to the CalenderContract Attendee documentation there is an ATTENDEE_TYPE prop that appears to not be assigned here.
Potentially assigning that could fix the issue?
Maybe I have some information that can help: I also tried it with another calendar app and seeing this in the logs of DAVx5
04-03 23:14:37.125 9258 15294 D davx5 : ], attendees=[ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=TRUE;PARTSTAT=ACCEPTED:mailto:[email protected] 04-03 23:14:37.125 9258 15294 D davx5 : , ATTENDEE;CN=GivenName;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:[email protected]While Simple Calendar produces this:
04-03 23:22:38.729 9258 15519 D davx5 : ], attendees=[ATTENDEE;CN=GivenName;CUTYPE=INDIVIDUAL;ROLE=NON-PARTICIPANT:mailto:[email protected]So there is no
RSVP=TRUEand the Role might be an issue. the organizer field seems right.(Log is from Debug output of DAVx5)
Which is the reason invites are not sent, according to Davx5
Here the other calendar app has the role set to REQ-PARTICIPANT whereas Simple Calendar results in NON-PARTICIPANT. Guessing it defaults to non-participant if not specified otherwise.
Hi there ! Any update about this issue ? I've the exactly same problem 4 years later
Thanks !