@rfc2822 Were you able to see the main issue described in the first post above? I don’t see any reply to it.
After much time and effort (it’s not trivial when you don’t do this all the time), I got everything I could from backups (lost all data for the week since the last backup), imported that data, reconfigured the calendars, installed DAVx5 again, and configured DAVx5 from scratch. DAVx5 worked 1 time, and now it just shows the all-white screen again.
I can’t enable verbose debugging because DAVx5 is completely frozen.
If I turn off the device’s screen and wait a while, the screen will come back on completely black. If I repeat that several times, DAVx5 will appear with an “IllegalStateException” that says “Must be called from main thread”.
When I click on “View Details”, I can load some debug output into a text editor. But when I try to save the file, I receive the error: “Permission Denial: writing androidx.core.content.FileProvider url content://at.bitfire.davdroid.debug/debug/debug-info.txt from pid=XXXXX, uid=XXXXX requires the provider be exported, or grantUriPermission()”.
I’ll spend more time on this and get that debug data for you one way or another, but it contains much private information, so it will take me awhile to go through it all and redact that data. Can you tell me what you really need from the debug file, so I can send just that section to you?
Note that pressing the back-arrow button on DAVx5’s “Debug info” screen just brings up another identical “Debug info” screen. I pressed it at least 20 times, and that’s all it does. There is no way I can find to get into the main DAVx5 UI at this point, as it is completely broken.
Note that I had no problems before this latest DAVx5 release and nothing else changed on my end.
(BTW, I tried to post this earlier, but pressing the “Submit” button on the Bitfire forums did nothing: no posting, no error message, and no feedback. I’m guessing you have some sort of rate-limiting imposed, as I made 1 tiny post just before I tried posting this. But please be aware that, if this is the cause of the issue, the user receives absolutely no feedback, so the UX is simply that the forums appear broken.)