Revision history [back]

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], 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), vCard 4.0

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], 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), vCard 4.0

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], 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.0](https://tools.ietf.org/html/rfc2426#section-3.1.1) vCard 4.0

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], 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) vCard 4.0
[3] [vCard 4.0](https://tools.ietf.org/html/rfc6350#section-6.2.1)

[EDIT][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.