Contacts generates invalid contacts

asked 2016-02-26 04:28:44 +0300

WhyNotHugo gravatar image

updated 2016-06-09 12:44:43 +0300

When synching via CardDav, the contacts app generates invalid contacts: either with missing FN (mandatory for vcard 3.0 and vcard 4.0), or missing N attributes(mandatory for vcard 3.0 only).

This is a violation of the specs[2][3], and while it gets sync'd to the server[1], it makes other clients fail/crash, it makes my desktop calendar app crash (due to invalid contacts which are parsed for birthdays), it breaks cascaded syncs, and backups, and forces me to manually edit vcard files before unbreaking everything but the phone (which is non-trivial, and extremely annoying if I happen to be in a hurry!).

[1] it actually works with radicale, because it doesn't validte anything, but fails with fastmail, which only accepts valid vcards.
[2] [vCard 3.0](https://tools.ietf.org/html/rfc2426#section-3.1.1)
[3] [vCard 4.0](https://tools.ietf.org/html/rfc6350#section-6.2.1)

[Update 2016-06-09]
This is still an issue 2.0.1.11. The Jolla phone still generates invalid contact files, so it's still impossible to sync them with vcard-complaint servers.

edit retag flag offensive close delete

Comments

Looks like the markdown parser is broken and isn't linking to rfc2426. :(

WhyNotHugo ( 2016-02-26 04:29:57 +0300 )edit
5

https://git.merproject.org/mer-core/buteo-sync-plugin-carddav/commit/9c7d183efb7524158599118e6c3a4fd340a0a8d9 resolves this issue, and will be released in 2.0.2.x.

chris.adams ( 2016-02-29 04:06:22 +0300 )edit

Thanks, that's great news!

WhyNotHugo ( 2016-02-29 04:20:25 +0300 )edit

Still missing FN, and on some contacts the jolla deletes the existing FN if you sync over carddav. The new owncloud version 9, does not show contacts with the missing FN, so this should be fixed soon.

poddl ( 2016-03-31 23:43:16 +0300 )edit

Could explain why google.com accepts vcard from Jolla but not Androids.

hoschi ( 2016-06-09 12:52:09 +0300 )edit