local storage error syncing addressbook
After many test I can say that this is a Davdroid problem: the contacts download cause the crash of process android.process.acore.
I had to export from Zimbra and import on Google Contacts to restore my contacts (a solution that I really doesn’t like ).
I don’t understand that because
android.process.acoredoes not belong to DAVdroid.
Is there any way to reproduce this problem? I’d really like to find a solution but everything is working here.
Hi, since some days I get exactly the same error. Here is the debug.txt
I can confirm that the “acore” breakdown is definitely connected to DAVdroid address book sync. It occurs only when I mark the contacts to be synced. The calendar sync works fine if the contacts are not marked.
With the proprietary app of my mail service (gmx.net), the contacts are synced without a problem, but when I use DAVdroid and the storage error occurs, it seems to corrupt the whole contact list until I switch it off again.
I hope this can be solved because I like DAVdroid much more for it’s simplicity.
From the debug.txt I just noticed that we use (almost) the same smartphone and android version. Maybe it is something very specific. Looks like this could make the debugging much more complicated. Any suggestions what we could try or additional information that could be useful?
Unfortunately, I don’t have an idea… and I guess it’s very specific, too. If you find out anything new, please let us know.
Hi, I am seeing the same error, the issues started as soon as I upgraded to DAVdroid 1.11-gplay. I have two Samsung galaxy devices which sync to the same Card DAV address books the device running DAVdroid 1.10 continues to work however the device that was updated to 1.11 shows the local storage error - %s error.
I have reinstalled DAVdroid and deleted the android contacts database however the error continues.
@cevans Hello, the debug logs are not accessible…
Same problem here with a bq M4.5 since a few days.
Tried with two devices, one with Android 5.1 and one with Android 6. Unfortunately I cannot copy the log for some reason.
Thanks for having a look into this!
@spot Unfortunately, we still don’t have an idea what the problem could be or how it could be reproduced. Any hints are appreciated…
The problem seems to occur primarily on Samsung devices with Android 5 or 6. Accessing SyncState seems to crash the contacts provider or some other important Android processes on those devices, so that further sync operations fail.
I’m working on a version which doesn’t use
ContactsContract.SyncStatefor testing purposes.
I was able to reproduce the problem on Android 5 and I guess the problem is caused by a memory leak which should be fixed with vcard4android/4da2606a.
I have sent another APK over email. Please tell me whether it now works for you.
@rfc2822 Sorry for the missing logs, https://paste.fedoraproject.org/paste/ass-QxxvNjhGJ1A0M58Y7w
@rfc2822 Have installed memory leak APK at initial force sync shows no errors. Will provide an update after a scheduled sync and some contact data changes. Looks very promising! thank you so much for your help.
I started getting this error today, the problem is that my contact list is emptied out after this but I get my contacts back after a restart, I do not know what is going on?
I have been using Davdroid for years, never had this issue. Also, I have not upgraded Davdroid for quite sometime. I also did not upgrade any of my system stuff. SO this has nothing to do with upgrades, it is weird that this issues suddenly started and experienced by peopel around the same time.
I am using Davdroid (Fdroid version) on Samsung Note 4, Lollipop with Nextcloud server.
Can i get a hold of the new apk as well?
@tartarian Hi, I was seeing the same issue with the default Android contacts client however, the latest DAVdroid build seems to have resolved all the issues. Sync is working perfectly in both directions and the contacts app is behaving correctly.
@cevans thanks, It looks like the update was rolled out yesterday.
1.11.1 is now available in F-Droid, too!