I think this is a DAVx5 issue.
After adding a new Zimbra account the device cannot synchronize:
First try: Sign in with URL and username
Base URL: https://zimbra.host.tdl
-> Result: DAVx5 recognized a calendar but with url https://zimbra.host.tld/myUser/Calendar
-> Because that calendar doesn’t exist: Error
Second try:
Base URL: https://zimbra.host.tld/dav
-> Result: Same as without /dav
Third try:
Base URL: https://zimbra.host.tld/dav/
-> Result: DAVx5 cannot find anything at all.
First/second try threw an exception:
at.bitfire.dav4jvm.exception.DavException: Expected 207 Multi-Status, got 200 OK
at at.bitfire.dav4jvm.DavResource.assertMultiStatus(DavResource.kt:17)
at at.bitfire.dav4jvm.DavResource.processMultiStatus(DavResource.kt:2)
at at.bitfire.dav4jvm.DavCalendar.multiget(DavCalendar.kt:10)
at at.bitfire.davdroid.syncadapter.CalendarSyncManager$downloadRemote$1.invoke(CalendarSyncManager.kt:2)
at at.bitfire.davdroid.syncadapter.CalendarSyncManager$downloadRemote$1.invoke(CalendarSyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.remoteExceptionContext(SyncManager.kt:1)
at at.bitfire.davdroid.syncadapter.SyncManager.remoteExceptionContext(SyncManager.kt:8)
at at.bitfire.davdroid.syncadapter.CalendarSyncManager.downloadRemote(CalendarSyncManager.kt:2)
at at.bitfire.davdroid.syncadapter.SyncManager$syncRemote$1$1$1.invokeSuspend(SyncManager.kt:2)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:3)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:18)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
at.bitfire.davdroid - 3.3.2-ose
