Unfortunately, the workaround breaks other things (the reason why we have sent the Accept header)…
I wonder whether it’s better to integrate it or not.
I have a similar issue like reported in this issue: https://forums.bitfire.at/topic/1843/davdroid-stops-syncing-without-throwing-an-error
Since a while I don’t recieve event updates anymore. The sync is started regularly like before, but the log doesn’t show any activity of an actual sync.
I.e. I create an event in the calendar but it doesn’t get synced to the server (nextcloud). Same of all of my accounts (including owncloud). I can confirm the server has not been updated in a long time (2y).
Everything worked fine a few weeks before.
Attached is the sync log.0_1538644505665_davdroid-25831-20181004-102417.txt
Please provide the DAVdroid debug info (DAVdroid / Settings / Debug info) as described in [READ BEFORE POSTING] What’s required to diagnose a problem.
Thanks! Ok so this is Linage, too, and for some reason the system doesn’t start synchronization. Can you have a look with adb, what happens when you force synchronization?
@varac According to the logs, synchronization is executed… is the problem still present? Is there anything in the logs you find suspicious?
Yes, the problem is still there, I create an event on my phone but it doesn’t show up on the nextcloud calendar.
Same for a second account which uses owncloud, so it’s definitivly the problem on the client side.
I also tried the other way, creating an event in nextcloud, it never reaches my phone’s calendar.
@varac According to the logs, there was nothing to synchronize. Are you sure that you have inserted the event into the right calendar?
Can you provide exact steps to reproduce (including what event you have created where and how, summary, start date, end date etc.) so that I can have a try? Maybe provide a test account?
Everything works here fine with Nextcloud, I use it everyday for myself…
@rfc2822 I can do that - is an adb logcat enough or do you need to have the debug log from the davdroid ui as well.
Damnit! Pebcak here, for some weird reason all calendars in “acalendar” were excluded from syncronisation. After I enabled them again, everything is fine again.
Sorry for the mess, and many thanks for your support!