Error "Couldn't parse multistatus XML element"

[dvdh1979]

Dear all,

I got the error "Couldn't parse multistatus XML element" on Android 12, DavX 4.3.16.1-ose and I have no idea how this suddenly came from and how to find out, which element causes the problem.

I am very thankful for any hint.

Best regards,
Dirk

[sunkup]

We won't know either without logs and/or debug information. You can share them with us and we may be able to find out what is going on.

Please see our FAQ entry to find out how to create debug infos.

[wouterjdb]

Having the same issue here I guess: Couldn't parse multistatus XML element

Maybe this helps?

07-03 20:18:46.655 24689 24747 W dav4jvm : EXCEPTION at.bitfire.dav4jvm.exception.InvalidPropertyException: XML text for DAV:Push:topic must not be empty
07-03 20:18:56.225 24689 27486 E davx5   : [syncadapter.SyncManager] HTTP/DAV exception
07-03 20:18:56.225 24689 27486 E davx5   : EXCEPTION at.bitfire.dav4jvm.exception.DavException: Couldn't parse multistatus XML element
07-03 20:19:29.746 24689 27984 E davx5   : [syncadapter.SyncManager] HTTP/DAV exception
07-03 20:19:29.746 24689 27984 E davx5   : EXCEPTION at.bitfire.dav4jvm.exception.DavException: Couldn't parse multistatus XML element
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.dav4jvm.DavResource.processMultiStatus(DavResource.kt:19)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.dav4jvm.DavResource.processMultiStatus(DavResource.kt:9)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.dav4jvm.DavCalendar.calendarQuery(DavCalendar.kt:68)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.CalendarSyncManager.listAllRemote$lambda$8(CalendarSyncManager.kt:37)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.CalendarSyncManager.$r8$lambda$0DPu49RVpRjQ244UrM7XEPeeN14(CalendarSyncManager.kt:1)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.CalendarSyncManager$$ExternalSyntheticLambda3.invoke(R8$$SyntheticClass:7)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.remoteExceptionContext(SyncManager.kt:1)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.remoteExceptionContext(SyncManager.kt:5)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.CalendarSyncManager.listAllRemote(CalendarSyncManager.kt:40)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.performSync$lambda$3$lambda$0(SyncManager.kt:12)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.$r8$lambda$pBA4_RZN0mkjmuFdtUJe8ed0RWw(SyncManager.kt:1)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager$$ExternalSyntheticLambda0.invoke(R8$$SyntheticClass:5)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager$syncRemote$1$1.invokeSuspend(SyncManager.kt:37)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager$syncRemote$1$1.invoke(SyncManager.kt:2)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager$syncRemote$1$1.invoke(SyncManager.kt:1)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:16)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:10)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager$syncRemote$1.invokeSuspend(SyncManager.kt:70)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:111)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:145)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source:105)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source:3)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.syncRemote(SyncManager.kt:39)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.performSync$lambda$3(SyncManager.kt:398)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.$r8$lambda$6JLScpXt9NTtUhR6ijwMNnVfhUU(SyncManager.kt:1)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager$$ExternalSyntheticLambda8.invoke(R8$$SyntheticClass:3)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:2)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:20)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.CalendarSyncer.sync(CalendarSyncer.kt:175)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.Syncer.onPerformSync(Syncer.kt:124)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.BaseSyncWorker$doSyncWork$2.invokeSuspend$lambda$1$lambda$0(BaseSyncWorker.kt:16)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfi
07-03 20:19:29.746 24689 27984 E davx5   : re.davdroid.syncadapter.BaseSyncWorker$doSyncWork$2.$r8$lambda$30qtTn2x03NjqWTyXgukbHTEYio(BaseSyncWorker.kt:1)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.BaseSyncWorker$doSyncWork$2$$ExternalSyntheticLambda0.invoke(R8$$SyntheticClass:13)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.InterruptibleKt$runInterruptible$2.invokeSuspend(Interruptible.kt:75)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.InterruptibleKt$runInterruptible$2.invoke(Interruptible.kt:13)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:16)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:41)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.InterruptibleKt.runInterruptible$default(Interruptible.kt:9)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.davdroid.syncadapter.BaseSyncWorker$doSyncWork$2.invokeSuspend(BaseSyncWorker.kt:497)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
07-03 20:19:29.746 24689 27984 E davx5   : 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:111)
07-03 20:19:29.746 24689 27984 E davx5   : 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
07-03 20:19:29.746 24689 27984 E davx5   : 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
07-03 20:19:29.746 24689 27984 E davx5   : 	at java.lang.Thread.run(Thread.java:1012)
07-03 20:19:29.746 24689 27984 E davx5   : Caused by: org.xmlpull.v1.XmlPullParserException: Unexpected token (position:TEXT 
07-03 20:19:29.746 24689 27984 E davx5   : Warning: DateTi...@3:1 in okhttp3.ResponseBody$BomAwareReader@8f51946) 
07-03 20:19:29.746 24689 27984 E davx5   : 	at com.android.org.kxml2.io.KXmlParser.next(KXmlParser.java:432)
07-03 20:19:29.746 24689 27984 E davx5   : 	at com.android.org.kxml2.io.KXmlParser.next(KXmlParser.java:313)
07-03 20:19:29.746 24689 27984 E davx5   : 	at at.bitfire.dav4jvm.DavResource.processMultiStatus(DavResource.kt:17)
07-03 20:19:29.746 24689 27984 E davx5   : 	... 44 more

[wouterjdb]

Still having the same issue. How can I narrow down the exact problem item?

[rfc2822]

You can enable verbose logging to get the whole logs: https://www.davx5.com/faq/how-to-debug

However it's very likely to be a Synology problem.

[wouterjdb]

Thanks - I'll give that a try. I expect there is somewhere a (single?) calendar item that has issues....

[wouterjdb]

Interesting turn of events. The moment I wanted to synchronize to get the error it worked. Turned out that the update I ran today (could/should have done that earlier) on the Synology NAS fixed the issue. See:

Case closed.