Sync error

jtg

I have been using DavDroid for quite some time. Some time ago it started throwing errors after each sync, albeit the syncs themselves succeed (or at least I haven’t found any difference between the server and my device yet).

The device in question is a Samsung S4 mini, running Android 4.4.2.

The relevant parts of the logcat output are as follows (filtered by egrep davdroid\|HttpClient\|Wire

I/davdroid.SyncManager(22907): Full synchronization forced 
I/davdroid.SyncManager(22907): Fetching remote resource list 
W/aCalendar( 3072): unknown calendar type bitfire.at.davdroid [...]
W/aCalendar( 3072): unknown calendar type bitfire.at.davdroid [...]
W/aCalendar( 3072): unknown calendar type bitfire.at.davdroid [...]
V/davdroid.URIUtils(22907): Normalized URI [...]
D/davdroid.WebDavResource(22907): Processing multi-status element [...]

The last two lines are repeated 4170 times, if I count it right.

E/davdroid.resource(22907): Ignoring unparseable entity in multi-response 
E/davdroid.resource(22907): at.bitfire.davdroid.resource.InvalidResourceException: No VEVENT without RECURRENCE-ID found 
E/davdroid.resource(22907):     at at.bitfire.davdroid.resource.Event.parseEntity(Event.java:131) 
E/davdroid.resource(22907):     at at.bitfire.davdroid.resource.WebDavCollection.multiGet(WebDavCollection.java:121) 
E/davdroid.resource(22907):     at at.bitfire.davdroid.syncadapter.SyncManager.pullNew(SyncManager.java:195) 
E/davdroid.resource(22907):     at at.bitfire.davdroid.syncadapter.SyncManager.synchronize(SyncManager.java:95) 
E/davdroid.resource(22907):     at at.bitfire.davdroid.syncadapter.DavSyncAdapter.onPerformSync(DavSyncAdapter.java:138) 
E/davdroid.resource(22907):     at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:259)

The block is repeated 18 times.

I/davdroid.SyncManager(22907): Fetching 0 updated remote resource(s) 
I/davdroid.SyncManager(22907): Removing entries that are not present remotely anymore (retaining 4151 entries) 
D/davdroid.Collection(22907): Committing 2 operations ... 
E/davdroid.DavSyncAdapter(22907): Local storage (content provider) exception 
E/davdroid.DavSyncAdapter(22907): at.bitfire.davdroid.resource.LocalStorageException: Couldn't access local content provider 
E/davdroid.DavSyncAdapter(22907):       at at.bitfire.davdroid.resource.LocalCollection.commit(LocalCollection.java:382) 
E/davdroid.DavSyncAdapter(22907):       at at.bitfire.davdroid.resource.LocalCalendar.deleteAllExceptRemoteNames(LocalCalendar.java:268) 
E/davdroid.DavSyncAdapter(22907):       at at.bitfire.davdroid.syncadapter.SyncManager.synchronize(SyncManager.java:99) 
E/davdroid.DavSyncAdapter(22907):       at at.bitfire.davdroid.syncadapter.DavSyncAdapter.onPerformSync(DavSyncAdapter.java:138) 
E/davdroid.DavSyncAdapter(22907):       at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:259) 
E/davdroid.DavSyncAdapter(22907): Caused by: android.os.TransactionTooLargeException 
E/davdroid.DavSyncAdapter(22907):       at android.os.BinderProxy.transact(Native Method) 
E/davdroid.DavSyncAdapter(22907):       at android.content.ContentProviderProxy.applyBatch(ContentProviderNative.java:510) 
E/davdroid.DavSyncAdapter(22907):       at android.content.ContentProviderClient.applyBatch(ContentProviderClient.java:377) 
E/davdroid.DavSyncAdapter(22907):       at at.bitfire.davdroid.resource.LocalCollection.commit(LocalCollection.java:372) 
E/davdroid.DavSyncAdapter(22907):       ... 4 more 
I/davdroid.DavSyncAdapter(22907): Sync complete for com.android.calendar

Any idea what might be going on?
–jtg

74alex

Hi, I experience the same problem.
Syncing with davdroid//0.8.4.1 from Owncloud 8.1.1 on a raspi to my samsung S5 mini (Android 4.4.2) I get the contacts synced in both directions and the list of calendars, but no entries in calendars and tasks.

In the logs I get
snippet.txt

–74alex

rfc2822

This seem too be two different problems.

@jtg Can you please post an example of your calendar (.ics) files?

@74alex When the ical4j library (which is used by DAVdroid) isn’t initialized correctly, this error may occur. Is this reproducible every time you start the sync process? Did you try to uninstall and re-install DAVdroid (there has been a change in the Manifest that might be related, and maybe the new Manifest hasn’t been processed somehow)?

jtg

Please see an example at the end of the message. I use a number of tools to access my calendar, however, so I’m not sure how characteristic this example is.
–jtg

BEGIN:VCALENDAR
PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Europe/Budapest
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
CREATED:20150909T132423Z
LAST-MODIFIED:20150913T132444Z
DTSTAMP:20150913T132444Z
UID:20150615T194833Z-17788@5e4ef32c5b50720d
SUMMARY:XXX
STATUS:CONFIRMED
X-MOZ-LASTACK:20150913T132444Z
DTSTART;TZID=Europe/Budapest:20150913T143000
DTEND;TZID=Europe/Budapest:20150913T183000
CLASS:PUBLIC
X-MOZ-GENERATION:2
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT15M
DESCRIPTION:XXX
END:VALARM
END:VEVENT
END:VCALENDAR

74alex

@rfc2822 I tried to reinstall but no effect. Still stops working. What should I do next?
–74alex

edit:
I reposted a new thread at ical4j-exception-when-syncing-calendars

jtg

A found another entry, that seems more interesting, by exporting the calendar using the “Calendar Import/Export” app and comparing it with the copy stored on the server. Quite a few of the entries show difference similar to the following (diff -u output, lines marked with + come from the version on the Android device). To the best of my knowledge, the entry was synced from the server to the device.

 BEGIN:VCALENDAR
 VERSION:2.0
 BEGIN:VTIMEZONE^M
 TZID:Europe/Budapest
+TZURL:http://tzurl.org/zoneinfo/Europe/Budapest
 X-LIC-LOCATION:Europe/Budapest
 BEGIN:DAYLIGHT
 TZOFFSETFROM:+0100
 TZOFFSETTO:+0200
 TZNAME:CEST
-DTSTART:19700329T020000
+DTSTART:19810329T020000
 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
 END:DAYLIGHT
 BEGIN:STANDARD
 TZOFFSETFROM:+0200
 TZOFFSETTO:+0100
 TZNAME:CET
-DTSTART:19701025T030000
+DTSTART:19961027T030000
 RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
 END:STANDARD
+BEGIN:STANDARD
+TZOFFSETFROM:+011620
+TZOFFSETTO:+0100
+TZNAME:CET
+DTSTART:18901001T000000
+RDATE:18901001T000000
+END:STANDARD
+BEGIN:DAYLIGHT
+TZOFFSETFROM:+0100
+TZOFFSETTO:+0200
+TZNAME:CEST
+DTSTART:19160501T000000
+RDATE:19160501T000000
+RDATE:19170416T030000
+RDATE:19180401T040000
+RDATE:19190415T040000
+RDATE:19200405T030000
+RDATE:19410406T020000
+RDATE:19430329T030000
+RDATE:19440403T030000
+RDATE:19450502T000000
+RDATE:19460331T030000
+RDATE:19470406T030000
+RDATE:19480404T030000
+RDATE:19490410T030000
+RDATE:19500417T030000
+RDATE:19540523T010000
+RDATE:19550523T010000
+RDATE:19560603T010000
+RDATE:19570929T030000
+RDATE:19800928T030000
+RDATE:19810927T030000
+RDATE:19820926T030000
+RDATE:19830925T030000
+RDATE:19840930T030000
+RDATE:19850929T030000
+RDATE:19860928T030000
+RDATE:19870927T030000
+RDATE:19880925T030000
+RDATE:19890924T030000
+RDATE:19900930T030000
+RDATE:19910929T030000
+RDATE:19920927T030000
+RDATE:19930926T030000
+RDATE:19940925T030000
+RDATE:19950924T030000
+END:STANDARD
+BEGIN:STANDARD
+TZOFFSETFROM:+0100
+TZOFFSETTO:+0100
+TZNAME:CET
+DTSTART:19180101T000000
+RDATE:19180101T000000
+RDATE:19450101T000000
+END:STANDARD
 END:VTIMEZONE
 BEGIN:VEVENT^M
-CREATED:20090901T191052Z
-LAST-MODIFIED:20140506T153523Z
-DTSTAMP:20140507T105125Z
+DTSTAMP:20150925T133939Z
 UID:040000008200E00074C5B7101A82E008000000000004278F5169CF0100000000000
  000001000000021E3128E0CB44D4A82B296ADA7C8DF1A
 SUMMARY:XXX
-CATEGORIES:Friends & Family
+ORGANIZER:xxx@xxx.hu
 DTSTART;TZID=Europe/Budapest:20090908T130000
 DTEND;TZID=Europe/Budapest:20090908T140000
 CLASS:PUBLIC
-SEQUENCE:0
-TRANSP:OPAQUE
 END:VEVENT
 END:VCALENDAR

Does this give some hint?
–jtg

jtg

@jtg
For the record, I no longer experience this issue. I’m now using version 0.9.1.3 but I suppose the problem went away with version 0.9.
Cheers:
–jtg