Revision history [back]
 | 1 | initial version | posted 2019-03-15 13:01:13 +0200  |
CalDAV calendar: msyncd fails when updating event with exceptions
I experience problems with a CalDAV account. After account creation, an event with lots of exceptions is immediately uploaded back to the server (msyncd logs Uploading exception modification via series update for local modification), but this upload fails with Network request failed with QNetworkReply::NetworkError: 299 and subsequent syncs always fail, because they first try to upload this exception modification again.
This obviously makes this calendar unusable. Interestingly, if I use EAS as backend for this calendar, the sync is also broken. I don't know if the same event causes it to fail, though. So probably the internal representation of events with exceptions may be the problem here.
For the record, I'm on SFOS 3.0.1 at this moment.
| | 2 | No.2 Revision |
CalDAV calendar: msyncd fails when updating event with exceptions
Update 2019-03-21: a malfunction with interpreting event exceptions has been found by @Damien Caliste. I'm testing a modified package at the moment which addresses part of the aspects of the malfunction.
I experience problems with a CalDAV account. After account creation, an event with lots of exceptions is immediately uploaded back to the server (msyncd logs Uploading exception modification via series update for local modification), but this upload fails with Network request failed with QNetworkReply::NetworkError: 299 and subsequent syncs always fail, because they first try to upload this exception modification again.
This obviously makes this calendar unusable. Interestingly, if I use EAS as backend for this calendar, the sync is also broken. I don't know if the same event causes it to fail, though. So probably the internal representation of events with exceptions may be the problem here.
For the record, I'm on SFOS 3.0.1 at this moment.
| | 3 | No.3 Revision |
CalDAV calendar: msyncd fails when updating event with exceptions
Update 2019-03-25: the modified package makes my calendar usable. I close this question as I expect the solution to be delivered in a future OS update.
Update 2019-03-21: a malfunction with interpreting event exceptions has been found by @Damien Caliste. I'm testing a modified package at the moment which addresses part of the aspects of the malfunction.
I experience problems with a CalDAV account. After account creation, an event with lots of exceptions is immediately uploaded back to the server (msyncd logs Uploading exception modification via series update for local modification), but this upload fails with Network request failed with QNetworkReply::NetworkError: 299 and subsequent syncs always fail, because they first try to upload this exception modification again.
This obviously makes this calendar unusable. Interestingly, if I use EAS as backend for this calendar, the sync is also broken. I don't know if the same event causes it to fail, though. So probably the internal representation of events with exceptions may be the problem here.
For the record, I'm on SFOS 3.0.1 at this moment.