Not syncing all contacts (new issue)



  • LOG 2

    12-27 14:25:35.636 I/davdroid.DavSyncAdapter(5750): Performing sync for authority com.android.contacts
    12-27 14:25:35.636 I/davdroid.WebDavResource(5750): Using preemptive authentication (not compatible with Digest auth)
    12-27 14:25:35.646 I/davdroid.SyncManager(5750): Remotely removing 0 deleted resource(s) (if not changed)
    12-27 14:25:35.646 I/davdroid.SyncManager(5750): Uploading 0 new resource(s) (if not existing)
    12-27 14:25:35.666 I/davdroid.SyncManager(5750): Uploading 0 modified resource(s) (if not changed)
    12-27 14:25:35.676 D/davdroid.HttpPropfind(5750): Prepared PROPFIND request: <propfind xmlns=“DAV:”>
    12-27 14:25:35.676 D/davdroid.HttpPropfind(5750): <prop>
    12-27 14:25:35.676 D/davdroid.HttpPropfind(5750): <CS:getctag xmlns:CS=“http://calendarserver.org/ns/”/>
    12-27 14:25:35.676 D/davdroid.HttpPropfind(5750): </prop>
    12-27 14:25:35.676 D/davdroid.HttpPropfind(5750): </propfind>
    12-27 14:25:36.476 D/davdroid.SNISocketFactory(5750): Setting SNI hostname
    12-27 14:25:37.396 I/davdroid.SNISocketFactory(5750): Established TLSv1 connection with $SERVER using TLS_DHE_RSA_WITH_AES_128_CBC_SHA
    12-27 14:25:37.916 D/davdroid.WebDavResource(5750): Received HTTP/1.1 207 Multi-Status
    12-27 14:25:37.946 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/
    12-27 14:25:37.946 D/davdroid.WebDavResource(5750): <?xml version=“1.0” encoding=“utf-8”?>
    12-27 14:25:37.946 D/davdroid.WebDavResource(5750): <d:multistatus xmlns:d=“DAV:” xmlns:s=“http://sabredav.org/ns” xmlns:card=“urn:ietf:params:xml:ns:carddav”><d:response><d:href>/remote.php/carddav/addressbooks/mimox/contacts/</d:href><d:propstat><d:prop><x3:getctag xmlns:x3=“http://calendarserver.org/ns/”>1388147136</x3:getctag></d:prop><d:status>HTTP/1.1 200 OK</d:status></d:propstat></d:response></d:multistatus>
    12-27 14:25:37.956 I/davdroid.SyncManager(5750): Fetching remote resource list
    12-27 14:25:37.976 D/davdroid.HttpPropfind(5750): Prepared PROPFIND request: <propfind xmlns=“DAV:”>
    12-27 14:25:37.976 D/davdroid.HttpPropfind(5750): <prop>
    12-27 14:25:37.976 D/davdroid.HttpPropfind(5750): <CS:getctag xmlns:CS=“http://calendarserver.org/ns/”/>
    12-27 14:25:37.976 D/davdroid.HttpPropfind(5750): <getetag/>
    12-27 14:25:37.976 D/davdroid.HttpPropfind(5750): </prop>
    12-27 14:25:37.976 D/davdroid.HttpPropfind(5750): </propfind>
    12-27 14:25:38.196 D/davdroid.WebDavResource(5750): Received HTTP/1.1 207 Multi-Status
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131110T182444.1384107884%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.cd051bd1ba%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.17dbd2f8d2%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.898fc3a865%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.0acf17195c%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.3320f1e7d3%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131130T142232.20b373e457%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.151769209b%2540$SERVER.vcf
    12-27 14:25:38.776 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.8c57876ba4%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.495727abf5%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.7913696a1f%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131130T142106.4b4b809a45%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.0fdf7d022c%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.fc0436a84c%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.4a2945d9de%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131130T143340.50b858c461%2540$SERVER.vcf
    12-27 14:25:38.786 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.f0d283e39f%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131115T225956.1384556396%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.0d19de2f23%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.ce16c99e96%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.2cae59f7e8%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.16b971642d%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.ff0344b1c3%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131130T143646.defacbb6e0%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.92c0d77fe9%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.804092dff6%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.5f5f705cf7%2540$SERVER.vcf
    12-27 14:25:38.796 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.639f44bab6%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.ffac9390a4%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131110T182445.1384107885%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122533.10a58d37d6%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122534.8cf6e1fe59%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131116T200830.1384632510%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.1c50f309a3%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.d9a4a1799f%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.43b97273fb%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.f0b230d866%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.d994c18625%2540$SERVER.vcf
    12-27 14:25:38.806 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131130T143545.6b8a9bd780%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.06e72d8a8e%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.2030e07bc1%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.3d8960188b%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131226T225742.a270be93bb%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.92809370ab%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.cfb35429cf%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.ea0824d3f4%2540$SERVER.vcf
    12-27 14:25:38.816 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131130T143459.b7f446c79e%2540$SERVER.vcf
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131110T182446.1384107886%2540$SERVER.vcf
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.14b81a5a78%2540$SERVER.vcf
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131201T195555.74ea814d0b%2540$SERVER.vcf
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.703440b44f%2540$SERVER.vcf
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.4597c5d829%2540$SERVER.vcf
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): Processing multi-status element: https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131227T122535.821399334f%2540$SERVER.vcf
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): <?xml version=“1.0” encoding=“utf-8”?>
    12-27 14:25:38.826 D/davdroid.WebDavResource(5750): <d:multistatus xmlns:d=“DAV:” xmlns:s=“http://sabredav.org/ns” xmlns:card=“urn:ietf:params:xml:ns:carddav”><d:response><d:href>/remote.php/carddav/addressbooks/mimox/contacts/</d:href><d:propstat><d:prop><x3:getctag xmlns:x3=“http://calendarserver.org/ns/”>1388147136</x3:getctag></d:prop><d:status>HTTP/1.1 200 OK</d:status></d:propstat><d:propstat><d:prop><d:getetag/></d:prop><d:status>HTTP/1.1 404 Not Found</d:status></d:propstat></d:response><d:response><d:href>/remote.php/carddav/addressbooks/mimox/contacts/20131110T182444.1384107884%2540$SERVER.vcf</d:href><d:propstat><d:prop><d:getetag>“f0a3c45dfce5a5d316727bcbc649c71f”</d:getetag></d:prop><d:status>HTTP/1.1 200 OK</d:status></d:propstat><d:propstat><d:prop><x3:getctag xmlns:x3=“http://calendarserver.org/ns/”/></d:prop><d:status>HTTP/1.1 404 Not Found</d:status></d:propstat></d:response><d:response><d:href>/remote.php/carddav/addressbooks/mimox/contacts/20131227T122532.cd051bd1ba%2540oc…
    12-27 14:25:39.066 I/davdroid.SyncManager(5750): Fetching 0 new remote resource(s)
    12-27 14:25:39.066 I/davdroid.SyncManager(5750): Fetching 0 updated remote resource(s)
    12-27 14:25:39.066 I/davdroid.SyncManager(5750): Removing non-dirty resources that are not present remotely anymore
    12-27 14:25:39.066 D/davdroid.LocalCollection(5750): Committing 1 operations
    12-27 14:25:39.096 I/davdroid.SyncManager(5750): Sync complete, fetching new CTag


  • developer

    Did you replace $SERVER and $PORT manually? The %2540 in the vcf names is OK?



  • Yes, $SERVER and $PORT are the two things I replaced manually. I am still checking the other point, will report soon



  • This is interesting… the URL with the “%2540” (like https://$SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131110T182444.1384107884%2540$SERVER.vcf) works, but with %40 (like $SERVER:$PORT/remote.php/carddav/addressbooks/mimox/contacts/20131110T182444.1384107884%40$SERVER.vcf) it works as well. In the web UI I see the files with just %40 btw.


  • developer

    Maybe older versions of DAVdroid and/or Owncloud created these file names… I suggest to export the contacts into a vcf file, deleted and re-create the address book on Owncloud, then importing the contacts and add the new address book into DAVdroid.



  • Maybe older versions of DAVdroid and/or Owncloud created these file names…

    Don’t think so

    I suggest to export the contacts into a vcf file, deleted and re-create the address book on
    Owncloud, then importing the contacts and add the new address book into DAVdroid.

    This is exactly what I did. Before, something broke umlaut characters (ö turned to ö etc) so I exported, fixed the cvf and re-imported. On the android side I stopped all apps accessing the contacts stroage and stoppend and wiped the storage, then re-enabled DAVdroid to sync again.


  • developer

    Do the UIDs in the .vcfs contain special characters, “@” etc? In this case you could try to sanitize them by using UUIDs or random numbers and then import again



  • Yes, owncloud creates UIDs like 20131226T225742.a270be93bb@my.server.com. So you think it makes sense to get rid of the “@my.server.com” and re-import?



  • So I just tried this now: removed all UIDs from the export file, reimport, OC regenerates UIDs (with @my.server.com), export again and delete the @my.server.com part, reimport. The result I got is actually the worst yet: only 43 of my 53 contacts made it into my android address book this time.

    The logcat still looks the same, so the problem does not seem to be related to any characters in the UIDs. I also double and tripple checked that the UIDs are unique.


  • developer

    Can you provide a test account for me where the problem is reproducible?



  • I could provide a test account but atm I do not have time to anonymize the data or minimize the test case. So, if you have some test data you would like to try on my server I can get you an account. Maybe we could rule out a problem with the data and/or davdroid this way and relay the bug to OC.


  • developer

    I can enter test data by myself but I don’t know if the problem will appear 😉



  • Just sent you a test account by email


  • developer

    @monreal Thanks got it. Please send another email address of you, too because Gmail has just decided to reject mails from our server.



  • Just replace @gmail.com with @gmx.net


  • developer

    I have tried with our test account on your server and uploaded 31 contacts. All 31 contacts have then been successfully synchronized with DAVdroid/0.5.6.



  • I found some time to test again today and in the end I got the sync working well. Here’s what I did:

    a) I removed the account configuration in DAVdroid and recreated it.
    b) I exported the contacts again and went through it line by line. The changes I did fall into these categories, maybe you find anything that could cause problems:

    1.)
    ITEM1.EMAIL;TYPE=INTERNET:someone@somewhere.com
    ITEM1.X-ABLABEL:Friends
    to
    EMAIL;TYPE=INTERNET:someone@somewhere.com

    2.)
    URL:http://server.com/?action=SOMETH
    ING&ID=324234
    to
    URL:http://server.com/?action=SOMETHING&ID=324234

    3.) I also removed one or two “” characters in address fields


  • developer

    Maybe the vcfs were corrupted. That would explain why DAVdroid/ez-vcard couldn’t read them. So I’ll close this issue.



  • Well it would be nice to know if ownCloud produced broken VCFs… so, were the cases 1-3 I listed above valid before I changed them manually (use of ITEM1. and ITEM.X-ABLABEL, splitting URLs over two lines and using “” to represent a newline)


Log in to reply
 

Similar topics