Steps to reproduce:
Set up a Caldav calendar (mailbox.org here).
With DAVx5 connect to this calendar.
Cause an sync error. In this case deleting a recurrent birthday reminder caused an error 403 (Forbidden) from the server.
DAVx5 writes a log file with technical error information (e. g. HTTP request and response, technical device information, Java stacktrace). The information might help the developer, but it doesn’t help a non-tech user at all.
The information about the failure appears as a tiny icon in the status bar only, where it can easily be overlooked.
DAVx5 informs the user in a visible message, in understandable, non-tech words that it could not synchronize, which item is affected (the displayed name of the contact, date or task), what caused the error, how he/she can solve the problem and go on. For instance see https://www.nngroup.com/articles/top-10-application-design-mistakes/, chapter 3.
If the log file is needed for the developer, DAVx5 helps the end-user with easy-to-follow steps to send it to the developer.
If you have a problem with DAVx⁵, please:
Try the latest DAVx⁵ version. Use the latest version of your server software, if applicable.
Read the Configuration, FAQ and manual pages carefully. The most common issues are explained there.
Try the forum search – most questions have already been answered.
Have a look at the debug info/error details/logs. You can often get an idea what’s the problem yourself.
Search the the Web for the problem, maybe ask friends who are willing to help.
Make sure that it’s not a server or networking problem. Search the FAQ/forums/bug tracker of your server software, too. Many supposed DAVx⁵ bugs are server or networking problems.
See also: FAQ: How to debug DAVx⁵-related problems
When posting, please provide as much information as you can:
Go to DAVx⁵ / Settings (left navigation drawer in the main screen) / Debug info. Send these information to yourself (using the “Share” action, for instance by email). Paste the info to fpaste.org or a similar service and provide a link. It contains the most important information about your device and configuration.
Describe exactly what you were doing (steps to reproduce), what you tried to achieve and what your problem is. Imagine someone else who wants to reproduce the problem to find a solution and provide all necessary information.
Give information about your environment: what is your server software (including version), what are your calendar URLs, do other clients work, etc.
If possible, try to explain what you already have tried to solve your problem.
If you get “No CalDAV/CardDAV service found” when you try to add an account:
Tap “View logs”. Send those logs to yourself (using the “Share” action, for instance by email).
Paste the logs to fpaste.org or a similar service and provide a link (feel free to let it expire in a month).
If you get an error notification while synchronizing:
Tap the notification. A debug info activity will appear.
Send the debug info to yourself (using the “Share” action, for instance by email).
Paste the debug info (≠ logs) to fpaste.org or a similar service and provide a link (feel free to let it expire in a month). Short debug output can be inserted in the text, but please quote with ``` (at the beginning and the end).
If additional logs are required to diagnose the problem, continue below.
Your problem doesn’t cause a notification or you need verbose logs?
DAVx⁵ / Settings (left navigation drawer in the main screen) / Enable “Verbose logging”. A permanent notification tells you that logging is now active.
Do whatever causes your problem (e.g. “Refresh calendars”, or initiate a sync).
Use the notification to share the log. You may have to expand the notification to see the “Share” action.
Send the logs to yourself (for instance by by email, or with Share with HTTP).
Remove private data from the logs, if applicable.
Paste the logs to fpaste.org or a similar service and provide a link (feel free to let it expire in a month). Short parts of the logs can be inserted in the text, but please quote with ``` (at the beginning and the end).
If your problem has been solved, it would be kind to let other people (who were willing to help you) know the actual solution.
debug info: show details of UnknownHostExceptions instead of an empty string
fix problems with events with VTIMEZONE with DAYLIGHT, but without STANDARD definition (events were always stored at 23:00 of previous day)
fix (potential) threading problem
notify on invalid tasks/vCard objects (events will follow)
add app setting for notification channels: Notification settings (only Android 8+)
use default time-zone to store floating DATE-TIMEs
exceptions of recurring events: use main event’s DTSTART time zone for RECURRENCE-ID
minor improvements and bug fixes
When you tap a notification about invalid iCalendar/vCard objects, you can see more information, including the URL of the invalid object. You can hide all “Sync warnings” in the app notification settings (Android 8+ only, because this depends on notification channels), but we recommend to care about these messages, because it means that some events/tasks could not be synchronized.
fixed: changed contacts visibility on every sync
fixed: crash on database upgrade
various refactoring and optimizations
Please note that if you upgrade from v <1.9 to 1.9.4 ≤ v < 1.9.10 directly, the upgrade will still fail (causing all collections to be shown as read-only without possibility to change that). In this case, you have to uninstall DAVdroid and install it again (or to delete all DAVdroid accounts, clear app storage and add the accounts again).
Upgrading from any version, including <1.9, to 1.9.10 should work without problems.
New in 1.8.1:
Better support for read-only address books:
discard local changes on read-only address books when syncing
show a notification when local changes are discarded
show warning when read-only address book is selected for sync in the DAVdroid account
DAVdroid is now written 100% in Kotlin!
rewrite of complete app to Kotlin finished (UI rewritten)
resource detection can now be cancelled (use the back button)
race condition in certificate handling fixed
other minor improvements and bug fixes
upgrade to okhttp/3.8.0 (should fix NoSuchElementException on empty DNS results)
remove “vcard4android” from VCard PRODID to avoid folding for better compatibility
use UUIDs for newly generated event/task UIDs (RFC 7986 5.3 UID Property)
added verbose information about current local and remote resource to debug info (helps to find faulty contacts/events, for instance when they’re not parseable)
new translations, which also fix a crash in the Spanish version
Address book sync.: fall back to PROPFIND when REPORT addressbook-query returns 400, 403, 500 or 501 (for instance, for old OwnCloud versions)
ical4android: treat empty-string task location and URL as null values
vcard4android: ignore raw contact data without MIMETYPE
gracefully ignore when server doesn’t sent Content-Type in GET responses
merge translations from Transifex