Well, I’m in a bit of a bad situation right now. The problem is that I have no access to the Horde server, can’t provide logs there, and therefore can’t file a bug report in Horde. Besides, convincing the Horde developers that the bug is at their side will be hard when essentially I will tell them “DAVdroid changed something and now it doesn’t work with Horde anymore”.
Firstly, I would like someone who runs their own Horde server, like @t-brink, to file that bug report with as much info as possible so this gets fixed.
In the meantime, users of DAVdroid should have a better option than just not using DAVdroid anymore, correct? Therefore I propose that either the DAVdroid developers try to reproduce this problem with Horde and find a workaround, or that the new auth method which seems the likely cause is given an advanced “disable” option.
Because really, the only alternative to any user of Horde at the moment is uninstalling DAVdroid completely (losing any changed calendar/contact info in the meantime on the phone) and then installing 0.8, and staying at 0.8 indefinitely until Horde fixes this bug. Which is probably going to take a while.
I know this situation sucks, but I believe DAVdroid should not introduce changes that completely break compatibility with one of the huge server softwares typically used with it. This is a critical bug.
I also politely ask to remove the “need info” label, since all the info that I can provide was already provided. I will try to be of any help I can, but I don’t know what to do at this point except switching to 0.8 and never updating DAVdroid again.