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.
Webcal subscriptions: handle webcal(s):// URLs and treat them as http(s)://
don’t use HTTP/2 with client certificates
minor bug fixes and improvements; new translations
OSE/standard build only (i.e. not the ones for Google Play):
show unhandled exceptions with DebugInfoActivity¹
¹ automatically handled by Google Play
It makes it possible to include new ciphers on an app-basis (packaged to the app) instead of only using the cipher suites which the base system provides. Because of that older devices with old systems like Android 4/5/6 are able to use more modern encryption techniques. At the end this makes the ecosystem more future-proof and more secure.
See the example we’ve posted here: https://twitter.com/davx5app/status/1128622058139717632 (2nd image)
Should be fixed with https://gitlab.com/bitfireAT/davx5-ose/commit/5709fd38d9df62ca0afc03e764487917fc9cc2e5 / 2.5.1, will send an APK for testing.
Install the new APK
Open DAVx⁵ and the account
Switch to Webcal tab
Swipe down to refresh the Webcal list
Subscribing to webcal(s):// URLs should now work
There are no such restrictions. Theoretically, you can sync hundreds of calendars, so I guess there’s another reason why some calendars don’t show up. Do those calendars have something in common, for instance are they shared calendars?
@synncgw I see, so the server previously sent Content-Encoding: gzip without actually using gzencode(), which caused the problems (no crash ).
In my opinion, okhttp/okio should accept 0-octet gzip responses nevertheless, but the specific problem should be fixed with your changes, so I have marked the topic as solved.