CardDav contacts remain even when deleted on the server

After synchronising the deletion from the server, only the data which was synchronised from the server will be deleted. That is, if you added any information to the contact locally (phone number, favorite, etc) the contact will remain on your device, as that local data will not be removed.

Once we upgrade to the newer QtPIM API, we are aiming to improve the synchronisation semantics with proper per-addressbook sync policies, but that's a little way off into the future.

Strange. So the contact should have been removed from the phone?

(I didn't change any details on the phone, thus the entire contact should fall into the category "data which was synchronised from the server".)

Yes, if that deletion is not being synced, that is a bug. Which type of CardDAV server are you using? And which version? Are you able to provide a test account at that server, which I can test with? Thanks!

@chris.adams, do you have any news regarding Carddav sync? Two years passed by and the issue is still present in Sailfish 2.2.0. Deletions on one side are not recognized on the other. I can give you an account on a test server running SabreDav.

Yeah this is what saddens me the most about Sailfish's development priorities: I can understand that many advanced features aren't there, but crippled contacts management?! Contacts are the most basic thing a phone should be capable of handling. Apart from the issues described here, we cannot even use multiple CardDav sources, since the phone won't ask to which of them new contacts should be added. So whatever new contact I add, it will go to into my business account, AFAIR. Maybe because "business" is before "personal" in alphabetical order. So before taking the risk of messing up my contacts, I add them by emailing it to my PC, adding it there to the CardDav server and then syncing back to Sailfish. Ugh.