Hi
Not sure if this problem is the same as the one in the other topics…
Here are the logs:
https://framabin.org/?2257e5b9a20420c1#64cbs2ehb7sWOY1vJBAfapXObwX4UeGiW1MC4hiBlTU=
Need something more?
(it hasn’t sync’ed since nov 7th)
Thanks
Hello,
The exception should not appear (should be fixed with commit 5ccdafa074c002454aa2512b52ac77582c303d44), but the root cause is that your VCard is invalid, see https://forums.bitfire.at/topic/832/0-9-0-4-contacts-syncing-regression-exception. Please fix your VCard and the error will be gone.
@rfc2822 Thank you very much… I didn’t know where to search! I had some difficulties to find which vcard I had to fix, so if someone has the same problem: I installed “alogcat root” from f-droid and found the URL (or URI?) of 3 vcards. I attached to those 3 vcards another image for the photo (I did that with “inverse Sogo connector 31.0.1”), and contacts now sync fine.
So I understand this is caused by the new version of davdroid? Because I hadn’t modified those contacts for a long time and before that update, I never had any problem.
If this is caused by Baïkal (which I haven’t updated for a long time), please tell me exactly what to report, because I’m not a devel at all 
@arBtfire said:
So I understand this is caused by the new version of davdroid? Because I hadn’t modified those contacts for a long time and before that update, I never had any problem.
It’s caused by an invalid VCard :); the new DAVdroid version just made the error visible.
If this is caused by Baïkal (which I haven’t updated for a long time), please tell me exactly what to report, because I’m not a devel at all
I don’t know where the invalid VCard comes from. Theoretically, a CardDAV server should send only valid VCards, but maybe it hast just stored and then delivered the VCard from another client.
@rfc2822 OK, thank you for the quick fix. As I don’t remember with which software I created these vcards, so I won’t report the problem.
Have a nice day
