Sailfish creates invalid vCard/VCF files (affects CardDav)

asked 2016-06-23 12:46:46 +0200

hammerhead gravatar image

updated 2016-06-23 15:42:55 +0200

Steps to reproduce:

  1. Edit any (valid) contact on the phone
  2. Sync via CardDav
  3. Realize that the VCF is now invalid(1) and fields are updated to a new format, even if they were never touched/edited(2) on the device

(1) With invalid I mean that they lack mandatory vCard fields like FN.

(2) It's important that untouched fields don't get updated. Otherwise contacts will always sync again with other devices even if nothing actually changed. Also, fields that Sailfish is unaware of will be lost. (I realize that this is most likely due to Sailfish creating vCard data on the fly from sqlite db entries and thus *is unable to even know what the original format of a field was.)*

edit retag flag offensive close delete


Duplicate of and as mentioned there, the issue with FN and N is fixed and will be released in the next update.

In regards to your second point, no, fields which the CardDAV plugin in SailfishOS cannot synchronise are not lost, they are stitched back into the regenerated vCard when upsyncing. See for the implementation.

chris.adams ( 2016-06-24 06:49:11 +0200 )edit

Is this solved, can this be closed @hammerhead?

BonoNL ( 2019-11-14 22:23:52 +0200 )edit

Since updating to 3.2 a couple of days ago, sync doesn't work at all. When trying to start it manually, the settings app just force closes.

hammerhead ( 2019-11-18 03:36:12 +0200 )edit