I'm running a DAViCal server with several clients (CalDAVzap, CalDAVSynch (Android) en iPad).
Recently I needed to reschedule a number of appointments. I did this using CalDAVzap. The changes included things like replacing repeating appointments by non-repeating appointments, and the other way around.
A short while after I completed the rescheduling the changes were synched to the iPads but the changes did not show on Android, despite several automatic and manual synchs. To be more precise, the removed entries were removed, but the replacement entries did not show up.
As a last resort I removed the CalDAVSynch account (with all data) and re-established it. After the initial synch the Android calendar was okay.
I'm aware that this kind of problems are very hard to find and solve. But is there anything I can do to help?
-- Johan
Hi Johan,
On 30 Jan 2014, at 14:11, Johan Vromans jvromans@squirrel.nl wrote:
I'm running a DAViCal server with several clients (CalDAVzap, CalDAVSynch (Android) en iPad).
Recently I needed to reschedule a number of appointments. I did this using CalDAVzap. The changes included things like replacing repeating appointments by non-repeating appointments, and the other way around.
A short while after I completed the rescheduling the changes were synched to the iPads but the changes did not show on Android, despite several automatic and manual synchs. To be more precise, the removed entries were removed, but the replacement entries did not show up.
As a last resort I removed the CalDAVSynch account (with all data) and re-established it. After the initial synch the Android calendar was okay.
I'm aware that this kind of problems are very hard to find and solve. But is there anything I can do to help?
try to reproduce the problem by creating an example and easily identifiable event (e.g. event text "QWERTYUIOP") and check the caldav_data table after each performed operation (SELECT caldav_data FROM caldav_data WHERE caldav_data LIKE '%QWERTYUIOP%';).
Then we can check the data changes on the server and identify whether there is an invalid event definition or it is CalDAV-Sync/Android issue.
JM
Ján Máté jan.mate@inf-it.com writes:
try to reproduce the problem by creating an example and easily identifiable event (e.g. event text "QWERTYUIOP") and check the caldav_data table after each performed operation (SELECT caldav_data FROM caldav_data WHERE caldav_data LIKE '%QWERTYUIOP%';).
Will do, later today.
-- Johan
So, did none of the new events show up or only a few of them?
It would have been interesting to see a log of a sync right after you changed the events (see http://dmfs.org/wiki/index.php?title=How_to_capture_a_log) At present we're not aware of any issues with missing events in CalDAV-Sync.
cheers
Marten
Am 30.01.2014 14:11, schrieb Johan Vromans:
I'm running a DAViCal server with several clients (CalDAVzap, CalDAVSynch (Android) en iPad).
Recently I needed to reschedule a number of appointments. I did this using CalDAVzap. The changes included things like replacing repeating appointments by non-repeating appointments, and the other way around.
A short while after I completed the rescheduling the changes were synched to the iPads but the changes did not show on Android, despite several automatic and manual synchs. To be more precise, the removed entries were removed, but the replacement entries did not show up.
As a last resort I removed the CalDAVSynch account (with all data) and re-established it. After the initial synch the Android calendar was okay.
I'm aware that this kind of problems are very hard to find and solve. But is there anything I can do to help?
-- Johan
Marten Gajda marten@dmfs.org writes:
So, did none of the new events show up or only a few of them?
IIRC none of the new events showed up, while the removed events did disappear.
It would have been interesting to see a log of a sync right after you changed the events (see http://dmfs.org/wiki/index.php?title=How_to_capture_a_log) At present we're not aware of any issues with missing events in CalDAV-Sync.
I haven't seen this before. I'll enable the debugging logs on the Androids and do my best to reproduce this.
-- Johan