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.
update ical4j: now allows UTC properties to have non-UTC values for compatibility
Account activity completely reworked
use tabs for CalDAV/CardDAV/Webcal
use RecyclerView, PagedList adapter and Room observeable queries for best performance even with huge lists
progress bars now also show pending syncs (semi-transparent bar without animation)
DavService: don’t delete all homesets/collections on refresh, but update only changed rows
vCard: use groupX. instead of davdroidX. for property grouping (so that there is no “davdroid” in the property name)
use Conscrypt to bring modern TLS versions/ciphers to all supported Android versions
use AndroidX Room for database access
many small improvements and bug fixes
Sorry if theis was not a “kind” posting, but after sitting for 3 hours with this and funbling in the dark, the frustration level was quite high. This PITA one gets for not accepting to share all personal data with G. by default.
Did you use the open-source version?
It did say 2.5-ose in the Subject, so if that is OpenSourceEdition then yes. Downloaded from the link on F-Droid.
Please feel free to (…)
I feel free to do such things in the open source projects I have been active in through the years, thanks.
we most probably won’t have any motivation to look at this problem
To motivate the fix of this bug (fixing a crash on user input is a serious bugfix and not a feature request) it should not be necessary to rub the right way. If this would have been closed source I would have be forced to give a one star rating (with refund if I would have payed for it) and move on. Instead you got a bug report which might be useful.
@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.
Probably all contacts which are edited otherwise are working. You can also edit a contact with photo in the Posteo Web interface and then Posteo will send the correct photo, which can then be synchronized.
@rfc2822 Afaik Nextcloud allows to store all kind of recurring events in the database, but lacks of a fully featured event editor. Currently I found these issue tickets related to the editing of recurring events:
New concept for entering recurrence rules / full-featured recurrence settings
special dialog when editing repeating events
@pescepalla Thank’s a lot! Your solution workes on my Xiaomi 5s plus with nextcloud on an own server in my LAN and using DAVx⁵ for synchronisation after I’ve searched two days where the problem comes from. By accident I installed nextcloud 15 and deleted and reconfigured DAVx⁵’s account. So I was not clear if it’s a nextcloud or a DAVx⁵ problem. Finally I found out in the nextcloud logs an entry
webdav Sabre\DAV\Exception\NotAuthenticated: No public access to this resource., No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured
Still misleading, I checked everything related with passwords and accounts.
Android doesn’t sync if it can’t connect to a working captive_portal_https_url, even if you choosed in the internet access settings for your network not to ask the question anymore and the internet works as far, as possible in China. And that with LineageOs. As many people not only using their own local nextcloud installation inside a LAN that is kind of a strange setting with Android in China at least.
Thanks again, @pescepalla !
HTTP 204 No Content must not have a body and thus Content-Length (which is the definition of 204). It seems like your server has returned HTTP 204 with a body, which does not make sense and can’t be interpreted. Please fix your Web server/application server.
Another thing which I don’t understand: Why even use X-APPLE-OMIT-YEAR if 1604 is assumed in any case? Why not just write partial dates as BDAY:1604-mm-dd (and assume that every date with 1604 is a partial date), wouldn’t it be the same?
Or does Apple use X-APPLE-OMIT-YEAR=1605 (or another non-1604-year) if the BDAY year is really 1604?
That is indeed a good question. I’ll try to do some tests when I get the next chance to test with an iPhone (I don’t have one myself).
Why can’t the server be improved so that it understands vCard 4?
Simply because the server is not under my control. I agree that upgrading the server really is the only way to add new features though.
Restrict Android to not offer partial dates in the contact schema at all, so that users cannot enter partial dates. This is how it has been until users have explicitly requested this feature because it’s available in Android and it’s available in vCard 4. Unfortunately, it’s not possible to (dis)allow partial dates according to server vCard 4 support because this support may change from sync to sync (and even if it wouldn’t, it can’t be set per account in Android).
I wasn’t aware of that.
So, there’s always a case with inconsistent behavior, which is a logical consequence of the fact that vCard 3 doesn’t support partial dates.
Now: Which case is more important?
To be honest, the arguments for both sides are pretty good and I’m no longer sure which one really is the best choice. (Maybe unless the answer to "
Or does Apple use X-APPLE-OMIT-YEAR=1605 (or another non-1604-year) if the BDAY year is really 1604?" is yes, since option 3 would probably cause the least loss in that case.)
yes I have, but I have to find an alternative way to reaching my NAS since I can’t just do https://nas.mydomain.com:8443 as I am using a reverse proxy to make sure my subdomains point to specific ports on the NAS.
My current setup is:
I have a subdomain (contacts.mydomain.com) (443) which points to my DDNS mydomain.ddns.net. The DDNS points to my network, and the 443 reaches my NAS, goes through a reverse proxy and points to a specific port in the NAS (in this case 8008). I need to do this to make sure I have a recognised SSL certificate from my domain.
Again, this setup works (if I open a browser and go to contacts.mydomain.com, it asks me username and password, and I can access the cardDAV (contacts.mydomain.com is sending me to http://192.168.1.200:8008/addressbooks/users/alex/ via reverse proxy).
I understand that DAVx5 wants a diskstation.example.com:8443 type of address, but I can’t just appent the port number to my nas address, as it would not recognize the SSL cert
No, in the eGroupware I could change the color of a category but not of a infolog.
In the past I could do it in the caldav Programm (also for the cards part)
Open Task have also no option to change the color.
So this could be a feature request for davx5