Revision history [back]

This is a very specific problem with ownCloud carddav sync. It seems that any contact that contains UID in form that has @servername in the end won't sync from server to Jolla phone. All contacts created directly on ownCloud versions earlier than 8.1.0 may have UID in this form (or at least some versions of ownCloud 7.x.x, not sure about 8.0.3 - 8.0.5).

At first I thought it was caused by buggy Contacts application in OC 8.1.0. But since Android based CardDAV works with the same server, and the contacts have been working previously with Jolla too, it is likely to be caused by SailfishOS implementation.

How to reproduce:

Export all contacts from ownCloud. In a resulting vcf file change UID in under one contact so that it does not contain @servername in the end of the line. Delete all contacts on the server (and on the phone). Import vcf file in ownCloud.

Result:

Activate sync on Jolla. Only the contact with UID that does not have @servername are synced and/or visible in SailfishOS Contacts-app.

When looking at the database of ownCloud, it seems that UID in contact information is used to create vCard uri. With contacts that don't get synced, this uri is in form 3ba1e245-a02d-4a1f-2006-535be06c394e@servername.vcf

I will follow instructions from caldav case and send the logs to Jolla.

This is a very specific problem with ownCloud carddav sync. It seems that any contact that contains UID in form that has @servername in the end won't sync from server to Jolla phone. All contacts created directly on ownCloud versions earlier than 8.1.0 may have UID in this form (or at least some versions of ownCloud 7.x.x, not sure about 8.0.3 - 8.0.5).

At first I thought it was caused by buggy Contacts application in OC 8.1.0. But since Android based CardDAV works with the same server, and the contacts have been working previously with Jolla too, it is likely to be caused by SailfishOS implementation.

How to reproduce:

Export all contacts from ownCloud. In a resulting vcf file change UID in under one contact so that it does not contain @servername in the end of the line. Delete all contacts on the server (and on the phone). Import vcf file in ownCloud.

Result:

ownCloud. Activate sync on Jolla. Jolla.

Result:

Only the contact with UID that does not have @servername are synced and/or visible in SailfishOS Contacts-app.

When looking at the database of ownCloud, it seems that UID in contact information is used to create vCard uri. With contacts that don't get synced, this uri is in form 3ba1e245-a02d-4a1f-2006-535be06c394e@servername.vcf

I will follow instructions from caldav case and send the logs to Jolla.

This is a very specific problem with ownCloud carddav sync. It seems that any contact that contains UID in form that has @servername in the end won't sync from server to Jolla phone. All contacts created directly on ownCloud versions earlier than 8.1.0 may have UID in this form (or at least some versions of ownCloud 7.x.x, not sure about 8.0.3 - 8.0.5).

At first I thought it was caused by buggy Contacts application in OC 8.1.0. But since Android based CardDAV works with the same server, and the contacts have been working previously with Jolla too, it is likely to be caused by SailfishOS implementation.

How to reproduce:

Export all contacts from ownCloud. In a resulting vcf file change UID in under one contact so that it does not contain @servername in the end of the line. Delete all contacts on the server (and on the phone). Import vcf file in ownCloud. Activate sync on Jolla.

Result:

Only the contact with UID that does not have @servername are synced and/or become visible in SailfishOS Contacts-app.

When looking at the database of ownCloud, it seems that UID in contact information is used to create vCard uri. With contacts that don't get synced, this uri is in form 3ba1e245-a02d-4a1f-2006-535be06c394e@servername.vcf

I will follow instructions from caldav case and send the logs to Jolla.

This is a very specific problem with ownCloud carddav sync. It seems that any contact that contains UID in form that has @servername in the end won't sync from server to Jolla phone. All contacts created directly on ownCloud versions earlier than 8.1.0 may have UID in this form (or at least some versions of ownCloud 7.x.x, not sure about 8.0.3 - 8.0.5).

At first I thought it was caused by buggy Contacts application in OC 8.1.0. But since Android based CardDAV works with the same server, and the contacts have been working previously with Jolla too, it is likely to be caused by SailfishOS implementation.

How to reproduce:

Export all contacts from ownCloud. In a resulting vcf file change UID in under one contact so that it does not contain @servername in the end of the line. Delete all contacts on the server (and on the phone). Import vcf file in ownCloud. Activate sync on Jolla.

Result:

Only the contact with UID that does not have @servername are is synced and/or become visible in SailfishOS Contacts-app.

When looking at the database of ownCloud, it seems that UID in contact information is used to create vCard uri. With contacts that don't get synced, this uri is in form 3ba1e245-a02d-4a1f-2006-535be06c394e@servername.vcf

I will follow instructions from caldav case and send the logs to Jolla.

This is a very specific problem with ownCloud carddav sync. It seems that any contact that contains UID in form that has @servername in the end won't sync from server to Jolla phone. All contacts created directly on ownCloud versions earlier than 8.1.0 may have UID in this form (or at least some versions of ownCloud 7.x.x, not sure about 8.0.3 - 8.0.5).

At first I thought it was caused by buggy Contacts application in OC 8.1.0. But since Android based CardDAV works with the same server, and the contacts have been working previously with Jolla too, it is likely to be caused by SailfishOS implementation.

How to reproduce:

Export all contacts from ownCloud. In a resulting vcf file change UID in under one contact so that it does not contain @servername in the end of the line. Delete all contacts on the server (and on the phone). Import vcf file in ownCloud. Activate sync on Jolla.

Result:

Only the contact with UID that does not have @servername is synced and/or become visible in SailfishOS Contacts-app.

When looking at the database of ownCloud, it seems that UID in contact information is used to create vCard uri. With contacts that don't get synced, this uri is in form 3ba1e245-a02d-4a1f-2006-535be06c394e@servername.vcf

I will follow instructions from caldav case and send the logs to Jolla.

This is a very specific problem with ownCloud carddav sync. It seems that any contact that contains UID in form that has @servername in the end won't sync from server to Jolla phone. All contacts created directly on ownCloud versions earlier than 8.1.0 may have UID in this form (or at least some versions of ownCloud 7.x.x, not sure about 8.0.3 - 8.0.5).

At first I thought it was caused by buggy Contacts application in OC 8.1.0. But since Android based CardDAV works with the same server, and the contacts have been working previously with Jolla too, it is likely to be caused by SailfishOS implementation.

How to reproduce:

Export all contacts from ownCloud. In a resulting vcf file change UID in under one contact so that it does not contain @servername in the end of the line. Delete all contacts on the server (and on the phone). Import vcf file in ownCloud. Activate sync on Jolla.

Result:

Only the contact with UID that does not have @servername is synced and/or become visible in SailfishOS Contacts-app.

When looking at the database of ownCloud, it seems that UID in contact information is used to create vCard uri. With contacts that don't get synced, this uri is in form 3ba1e245-a02d-4a1f-2006-535be06c394e@servername.vcf

I will follow instructions from caldav case and send the logs to Jolla.

Update 21 Oct 2015: Looks like the fixes in buteo-plugins and introduced in 1.1.9.28 worked after all. After upgrade to ownCloud 8.2 and OC contacts app reinstallation, the contacts with @-character in their UIDs have synced properly. properly. It is very possible that there were bugs in both ends. Closing this question now.

This is a very specific problem with ownCloud carddav sync. It seems that any contact that contains UID in form that has @servername in the end won't sync from server to Jolla phone. All contacts created directly on ownCloud versions earlier than 8.1.0 may have UID in this form (or at least some versions of ownCloud 7.x.x, not sure about 8.0.3 - 8.0.5).

At first I thought it was caused by buggy Contacts application in OC 8.1.0. But since Android based CardDAV works with the same server, and the contacts have been working previously with Jolla too, it is likely to be caused by SailfishOS implementation.

How to reproduce:

Export all contacts from ownCloud. In a resulting vcf file change UID in under one contact so that it does not contain @servername in the end of the line. Delete all contacts on the server (and on the phone). Import vcf file in ownCloud. Activate sync on Jolla.

Result:

Only the contact with UID that does not have @servername is synced and/or become visible in SailfishOS Contacts-app.

When looking at the database of ownCloud, it seems that UID in contact information is used to create vCard uri. With contacts that don't get synced, this uri is in form 3ba1e245-a02d-4a1f-2006-535be06c394e@servername.vcf

I will follow instructions from caldav case and send the logs to Jolla.

Workaround:

If you are still getting this problem with Sailfish 1.1.9.28 and onwards with ownCloud 8.2 or newer, you can fix the contacts manually by first exporting them from your owncloud instance. After this delete all contacts in owncloud instance. In exported VCF file remove all UID endings with @ in them using a text editor, and import the file to the owncloud again. After this the sync should work.

Update 21 Oct 2015: Looks like the fixes in buteo-plugins and introduced in 1.1.9.28 worked after all. After upgrade to ownCloud 8.2 and OC contacts app reinstallation, the contacts with @-character in their UIDs have synced properly. It is very possible that there were bugs in both ends. Closing this question now.

Test method: Tested with new imported contact containing UID with @-char, synced it on phone, and exported it again to see that the @-char has not been removed by original import.

There is a small chance that owncloud app has moved to using something else than UID as a base for vcard URLs. If this is the case, this can be opened again.