Not working with owncloud 5.0.11 (debian)



  • I’m using owncloud 5.0.12 on Ubuntu, and couldn’t log in yesterday due to the other bug, but now I can log in but a sync never finishes, here is a snippet from logcat:

    s/user%40example.org/contacts/78308dc3df.vcf</d:href><d:propstat><d:prop><card:address-data>BEGIN:VCARD&#13;
    D/davdroid.WebDavCollection(28964): VERSION:3.0&#13;
    D/davdroid.WebDavCollection(28964): FN:supportdesk@miamioh.edu&#13;
    D/davdroid.WebDavCollection(28964): N:supportdesk@miamioh.edu;;;;&#13;
    D/davdroid.WebDavCollection(28964): EMAIL;TYPE=INTERNET:supportdesk@miamioh.edu&#13;
    D/davdroid.WebDavCollection(28964): UID:78308dc3df&#13;
    D/davdroid.WebDavCollection(28964): REV:2013-09-18T16:06:37+00:00&#13;
    D/davdroid.WebDavCollection(28964): PRODID:-//ownCloud//NONSGML Contacts 0.2.5//EN&#13;
    D/davdroid.WebDavCollection(28964): END:VCARD&#13;
    D/davdroid.WebDavCollection(28964): </card:address-data><d:getetag>"01b241be2fc152ac6d656bbfe29f05ea"</d:getetag></d:prop><d:status>HTTP/1.1 200 OK</d:status></d:propstat></d:response><d:response><d:href>/owncloud/remote.php/carddav/add
    D/dalvikvm(28964): GC_CONCURRENT freed 1386K, 37% free 7781K/12192K, paused 2ms+7ms, total 58ms
    D/dalvikvm(28964): GC_CONCURRENT freed 4319K, 55% free 5489K/12192K, paused 3ms+11ms, total 63ms
    D/dalvikvm(28964): GC_CONCURRENT freed 1844K, 54% free 5691K/12192K, paused 2ms+10ms, total 71ms
    D/dalvikvm(28964): WAIT_FOR_CONCURRENT_GC blocked 25ms
    I/PropertyFactoryRegistry(28964): Not a default property: [X-MOZILLA-HTML]
    D/dalvikvm(28964): GC_CONCURRENT freed 1979K, 53% free 5756K/12192K, paused 3ms+8ms, total 58ms
    D/dalvikvm(28964): WAIT_FOR_CONCURRENT_GC blocked 19ms
    I/PropertyFactoryRegistry(28964): Not a default property: [X-MOZILLA-HTML]
    D/dalvikvm(28964): GC_CONCURRENT freed 1958K, 53% free 5845K/12192K, paused 1ms+7ms, total 59ms
    D/dalvikvm(28964): WAIT_FOR_CONCURRENT_GC blocked 32ms
    I/PropertyFactoryRegistry(28964): Not a default property: [X-MOZILLA-HTML]
    D/dalvikvm(28964): GC_CONCURRENT freed 1955K, 52% free 5913K/12192K, paused 3ms+12ms, total 76ms
    I/PropertyFactoryRegistry(28964): Not a default property: [X-MOZILLA-HTML]
    I/PropertyFactoryRegistry(28964): Not a default property: [X-MOZILLA-HTML]
    I/PropertyFactoryRegistry(28964): Not a default property: [X-MOZILLA-HTML]
    D/dalvikvm(28964): GC_CONCURRENT freed 1958K, 51% free 5987K/12192K, paused 3ms+8ms, total 53ms
    D/dalvikvm(28964): GC_CONCURRENT freed 1971K, 51% free 6064K/12192K, paused 3ms+17ms, total 92ms
    D/dalvikvm(28964): WAIT_FOR_CONCURRENT_GC blocked 43ms
    I/PropertyFactoryRegistry(28964): Not a default property: [X-MOZILLA-HTML]
    E/davdroid.ContactsSyncAdapter(28964): net.fortuna.ical4j.data.ParserException: Error at line 5:Error parsing line
    D/SyncManager(  480): failed sync operation user@example.org@mail.example.org/owncloud/remote.php/carddav/ u0 (bitfire.at.davdroid), com.android.contacts, USER, earliestRunTime 46461667, reason: 1000, SyncResult: stats [ numParseExceptions: 1]
    D/SyncManager(  480): not retrying sync operation because the error is a hard error: user@example.org@mail.example.org/owncloud/remote.php/carddav/ u0 (bitfire.at.davdroid), com.android.contacts, USER, earliestRunTime 46479815, reason: 1000
    D/AccountTypeManager(28143): Registering external account type=bitfire.at.davdroid, packageName=at.bitfire.davdroid
    E/ExternalAccountType(28143): Problem reading XML in line 4 for external package at.bitfire.davdroid
    E/ExternalAccountType(28143): com.android.contacts.common.model.account.AccountType$DefinitionException: supportsPhoneticFamilyName must be true
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.account.BaseAccountType$NameKindBuilder.checkAttributeTrue(BaseAccountType.java:860)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.account.BaseAccountType$NameKindBuilder.parseDataKind(BaseAccountType.java:893)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.account.BaseAccountType$KindParser.parseDataKindTag(BaseAccountType.java:719)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.account.BaseAccountType.parseEditSchema(BaseAccountType.java:657)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.account.ExternalAccountType.inflate(ExternalAccountType.java:362)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.account.ExternalAccountType.<init>(ExternalAccountType.java:126)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.account.ExternalAccountType.<init>(ExternalAccountType.java:96)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.AccountTypeManagerImpl.loadAccountsInBackground(AccountTypeManager.java:429)
    E/ExternalAccountType(28143):   at com.android.contacts.common.model.AccountTypeManagerImpl$4.handleMessage(AccountTypeManager.java:303)
    E/ExternalAccountType(28143):   at android.os.Handler.dispatchMessage(Handler.java:99)
    E/ExternalAccountType(28143):   at android.os.Looper.loop(Looper.java:137)
    E/ExternalAccountType(28143):   at android.os.HandlerThread.run(HandlerThread.java:61)
    

    It looks like a parseerror on an entry, but I don’t know why or how to fix it.

    Also the new version isn’t on f-droid yet, so I had to compile it myself from the latest git checkout.


  • developer

    Could you please test 0.3.4-alpha?



  • If i Know how to compile it, yes.



  • Hello,

    I installed yesterday the latest 0.3.4 available on f-droid. Now, no more error seems to be reported by davdroid, but I’m unable to see my contacts in “people” app; and it seems to be the same case for the calendar.

    I’ll try to provide some logcat output tomorrow evening (not available this evening, and device is at home).

    Cheers,

    C.



  • Hey,

    It worked for me. I just had to remove and re-add the accounts. Hope it works for you too.

    Jeanneret Cedric notifications@github.com wrote:

    Hello,

    I installed yesterday the latest 0.3.4 available on f-droid. Now, no more error seems to be reported by davdroid, but I’m unable to see my contacts in “people” app; and it seems to be the same case for the calendar.

    I’ll try to provide some logcat output tomorrow evening (not available this evening, and device is at home).

    Cheers,

    C.


    Reply to this email directly or view it on GitHub.



  • Hello,

    hmm, weird, was a brand new account (I removed all the davdroid accounts on my device in order to prevent any problem with my data ;))…
    Will give it a new try tomorrow then. If this works… wow, I’ll be able to remove the two app needing google-play, meaning I’ll be free for good! Davdroid is only love :).



  • Just a short update from my side:
    After an update to owncloud 5.0.12 (from debian) and an update to DAVdroid 0.3.4-alpha from f-droid, DAVdroid still crashes. Removing and recreating the account on DAVdroid dose not change the behavior.



  • hmm, ok — here, owncloud 5.0.12 with 0.3.4, no crash, but no data for now.
    For information, it seems there will be some announce tomorrow regarding owncloud — it may be wise to just wait for it.



  • Better, but still no dice:

    I/davdroid.SyncManager(17517): Adding 72f8f10318.vcf
    I/davdroid.SyncManager(17517): Adding 30f1c4ce99.vcf
    I/davdroid.SyncManager(17517): Adding 4556b975f1.vcf
    I/davdroid.SyncManager(17517): Adding c567349f1e.vcf
    I/davdroid.SyncManager(17517): Adding c3fc0fe0d8.vcf
    I/davdroid.SyncManager(17517): Adding c98a47e1d9.vcf
    E/JavaBinder(17517): !!! FAILED BINDER TRANSACTION !!!
    E/davdroid.DavSyncAdapter(17517): Remote process (content provider?) died
    E/davdroid.DavSyncAdapter(17517): android.os.TransactionTooLargeException
    E/davdroid.DavSyncAdapter(17517):       at android.os.BinderProxy.transact(Native Method)
    E/davdroid.DavSyncAdapter(17517):       at android.content.ContentProviderProxy.applyBatch(ContentProviderNative.java:482)
    E/davdroid.DavSyncAdapter(17517):       at android.content.ContentProviderClient.applyBatch(ContentProviderClient.java:227)
    E/davdroid.DavSyncAdapter(17517):       at at.bitfire.davdroid.resource.LocalCollection.commit(LocalCollection.java:159)
    E/davdroid.DavSyncAdapter(17517):       at at.bitfire.davdroid.syncadapter.SyncManager.synchronize(SyncManager.java:147)
    E/davdroid.DavSyncAdapter(17517):       at at.bitfire.davdroid.syncadapter.DavSyncAdapter.onPerformSync(DavSyncAdapter.java:56)
    E/davdroid.DavSyncAdapter(17517):       at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:257)
    D/SyncManager(  482): failed sync operation user@domain.org@mail.domain.org/owncloud/remote.php/carddav/ u0 (bitfire.at.davdroid), com.android.contacts, USER, earliestRunTime 79202490, reason: 1000, SyncResult: databaseError: true stats [ numInserts: 505]
    D/AccountTypeManager(17577): Registering external account type=bitfire.at.davdroid, packageName=at.bitfire.davdroid
    W/ResourceType(17577): getEntry failing because entryIndex 196 is beyond type entryCount 77
    W/ResourceType(17577): Failure getting entry for 0x7f0200c4 (t=1 e=196) in package 0 (error -2147483647)
    I/AccountTypeManager(17577): Loaded meta-data for 3 account types, 2 accounts in 25ms(wall) 6ms(cpu)
    

    Maybe you need to split the transactions up into smaller chunks? I have 505 contacts and get that exception.



  • Am 23.10.2013 14:02, schrieb Travis Burtrum:

    Maybe you need to split the transactions up into smaller chunks? I
    have 505 contacts and get that exception.

    Could be. 0.3.4 worked for me and I only have roughly 150 contacts.


  • developer

    Closing this because there are many different issues and I don’t know which ones are related.

    I think I have fixed the “TransactionTooLargeException” issue with 0.3.5. and the parsing errors should be fixed since 0.3.4.

    Please test with 0.3.5 and if you still get errors, create a specific issue with logcat attached (if possible) and the exact problem.


Log in to reply
 

Similar topics

  • 2
  • 3
  • 1