Summary: | CardDav not syncing client changes with server | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Aqeel Zafar <aqeel> |
Component: | DAV Resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | greg, public, robn |
Priority: | NOR | ||
Version: | 1.13.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Aqeel Zafar
2015-01-22 12:25:56 UTC
Hi, I'm from FastMail, and I wrote the above on another forum when Aqeel asked me about it. This is using FastMail CardDAV. If you want to try it, create a trial account at fastmail.com, then go to https://www.fastmail.com/go/carddavbeta to enable CardDAV for your account. There's server settings at https://beta.fastmail.com/help/technical/servernamesandports.html. Just to add to the issue, the ETag that it the client is during the PUT is one it obtained earlier from a GET. The REPORT was in a response to an explicit sync request (F5 in kaddressbook). It updated the contact, but doesn't appear to have updated the stored etag. I'll need to do more testing to see the exact order of events. I'm not sure when I'll get to that testing; hopefully today. It should be easy for you to reproduce though. I think this is a duplicate of bug #338570. Hey, Yup, it's indeed the same issue as for #338570. Merging, and it's fixed for 4.4.10 normally. Cheers, Grégory *** This bug has been marked as a duplicate of bug 338570 *** |