CardDAV: only new contacts get synced

asked 2016-10-02 13:57:37 +0300

gnuheidix gravatar image

updated 2016-10-02 15:12:54 +0300

I have the problem, that only newly added contacts are being synced to the server / from the server.

How does the CardDAV synchronization process determine, what contact entries need to be added to the server?

Some months ago, I once successfully synced all my contacts from the phone to my server but I noticed, that I want the contacts synced to another account. I changed the DAV accounts in the accounts settings and triggered a sync, but no entries are being transferred since then unless a completely new one gets added to the phone / the server.

I've checked the Sync Logs for anomalies (AMR appears to be always 000), scrolled through the source code, commits and issues of buteo-sync-plugin-carddav. I noticed the relation to the table OOB in the contacts.db. No luck yet. Any hints somebody?

Server software: Baikal 0.4.6

edit retag flag offensive close delete

Comments

What server software do you use? Radicale works fine for my contacts & my calendar ...

mrtrm ( 2016-10-02 15:04:07 +0300 )edit

This is working as intended for now (until we can update our backend to latest QtPIM API and properly support separated addressbooks locally on device). Currently the implemented behaviour is that only newly added or modified local-device contacts will be synced to online servers.

chris.adams ( 2016-10-04 09:04:58 +0300 )edit

@chris.adams Is there a way, how I can reset the mechanism manually, so it exports all contacts again against the server like it did once?

gnuheidix ( 2016-10-04 21:35:57 +0300 )edit

I haven't tested this, and it may not work and may cause you to lose data, so beware! But, if you export them to vcard, clear your contacts database, import from vcard, and then trigger a sync, that might work.

chris.adams ( 2016-10-11 06:20:53 +0300 )edit