@computingfroggy Thanks for the update. Good to hear that it now works!
Exceptions are not synchronized
-
Hi,
if I define an exception (EXDATE) in the calendar client on my pc the event does not disappear for the defined date. If I delete only one single event of an recurring event on my phone it creates multiple new events instead of adding an exception to the recurring event.
Greetings
Max -
Duplicate of #61, see also http://code.google.com/p/android/issues/detail?id=2229. I think this is an Android bug and not related to DAVdroid.
-
The issue referenced above says that it got fixed in CalDav, ie. the Connector, which makes me think that it might have to be fixed in DavDroid too.
-
@phmarek: I don’t understand your comment. This bug is in no way related to CalDAV but to the Android calendar provider. Please give further explanations.
-
You wrote above
I think this is an Android bug and not related to DAVdroid.
But http://code.google.com/p/android/issues/detail?id=2229 mentions that it got fixed not in Android, but in the CalDav App - which makes me think that possibly it would have to be fixed in DavDroid (which is a sync adapter, too), too.
-
But http://code.google.com/p/android/issues/detail?id=2229 mentions that it got fixed not in Android, but in the CalDav App - which makes me think that possibly it would have to be fixed in DavDroid (which is a sync adapter, too), too.
OK, it’s clear now, thanks.
(What is the “CalDav App”? There are several ones.) Assuming you mean CalDav-Sync, I guess that it handles event instances itself instead of relying on the Android calendar provider – this is a different design approach and can’t be done with DAVdroid. DAVdroid relies on the Android API for recurring events, and when the Android API is bugged, the bug has to be fixed there. Also, CalDav-Sync isn’t open-source (yet? although this has been promised), so I think it doesn’t provide any benefit to know what CalDav-Sync is able to do.
