Thanks Marten, will check & fix in the next version. JM On Jul 2, 2013, at 2:04 PM, Marten Gajda <marten@dmfs.org> wrote:

Hi Felix,

I hope you don't mind that I include the CalDavZAP mailing list (I've BBC'ed you).

The problem is that Android doesn't actually delete instances of a recurring event. Instead Android creates an exception and sets the status to "cancelled". My app synchronizes the event just like that. The app could try to fix that automatically, but I think converting a "cancelled" exception to a deleted event would be wrong. The app should sync events, not modify them.

What you see in CalDavZAP is a bug in the exception handling of CalDavZap. I've attached an event that shows the problem. It's a recurring event (it recurs every Tuesday, Wednesday and Thursday). The instances on 2013-07-03 and 2013-07-04 have been deleted in Android, i.e. their status is set to "CANCELLED".

CalDavZap shows the original event + the exceptions. I think the correct behavior would be to show the exception crossed out. That's what most clients to with cancelled events.

cheers

Marten

Am 02.07.2013 13:14, schrieb Felix:

...

Hi there,

i am using caldav-sync on cyanogenmod 10.1 with an davical-server 1.1.1-1 on debian and caldavzap as web-frontend. When i have a repeating event and delete one occurence of it in android, caldavzap still shows the deleted event in addition to a clone of the event without repeatitions. Android does not show these events.

Best regards, Felix

-- Marten Gajda Schandauer Straße 34 01309 Dresden Germany

tel: +49 177 4427167 email: marten@dmfs.org twitter: twitter.com/dmfs_org

VAT Reg. No.: DE269072391

-- Marten Gajda Schandauer Straße 34 01309 Dresden Germany

tel: +49 177 4427167 email: marten@dmfs.org twitter: twitter.com/dmfs_org

VAT Reg. No.: DE269072391 <850bad7c-e116-4045-a2c6-ff04076c1e34.ics>