@KrisWebDev DAVdroid has only very limited support for iTIP (where CANCEL is defined) and CalDAV Scheduling. Shouldn’t the cancellation be processed by the server, which then only sends the modified object to the client (i.e. DAVdroid)? I’m honest that I didn’t work through the iTIP/CalDAV Scheduling standards yet … (and they’re not part of plain CalDAV, and at the moment, DAVdroid doesn’t claim to support them).
Also, this is not related to the original post which is about events with STATUS:CANCELLED, which is a plain iCalendar property and doesn’t require iTIP/CalDAV scheduling, so I’ll move this into an extra thread.