I really delete the calendar from DavDroid.
But you're right, now I have the confirmation dialogue:
Well ... I do not understand, my version was downloaded recently on F-droid. The most important thing is that it works now, thanks rfc2822 !
@xyzzy said in Support for SSL client certificate and Basic/Digest at same time:
I neither change the authentication method of the groupware server nor the certificate requirement of the proxy server before the groupware server. For me it would be good enough if I could specify user/password in the base url. But davdroid seems to remove this part of the url.
It doesn't remove anything, but it doesn't use username/password from the URL. At the moment, DAVdroid unfortunately only supports username/password or client certificates as authentication, but not both because client certificates are implemented as an authentification method.
BTW, I cannot reply using firefox 59.0.2. In the webconsole I get:
I'm typing this reply with Firefox 59.0.2 (MozillaFirefox-59.0.2-lp150.1.6.x86_64 from OpenSUSE Leap 15 Beta). If you can find out what the problem is, it would be kind if you could report it to NodeBB directly. We're currently using NodeBB 1.8.2 (latest release) without modifications.
If you have a problem with DAVdroid, please:
Try the latest DAVdroid version. Use the latest version of your server software, if applicable.
Read the Configuration and FAQ pages carefully. The most common issues are explained there.
Use the forum search! Most questions have already been answered.
Search the the Web for the problem, maybe ask friends who are willing to help.
Make sure that it's not a server problem. Search the FAQ/forums/bug tracker of your server software, too. Many supposed DAVdroid bugs are server (configuration) problems.
Provide helpful and verbose information!
If you expect other people to help you, provide as much information as you can. It's no fun to debug a problem without knowing about what's actually the problem.
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.
Important: Go to DAVdroid / 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.
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?
DAVdroid / Settings (left navigation drawer in the main screen) / Enable "log to external storage." A notification with the log file path appears.
Do whatever causes your problem (e.g. "Refresh calendars", or initiate a sync).
Disable "log to external storage" again. Please keep in mind that those log files may contain private information and are accessible by any app which has the permission to access external storage, so delete them after those steps.
Send the logs to yourself (e.g. in the file manager and then send by email, or use the brilliant app 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.
new sync logic (preparation for Collection Sync, uses less memory)
"retry" and "view item" actions for sync errors
I/O errors are shown as minimum priority notifications (which are not shown in the notification bar, but when the notification drawer is pulled down)
notifications will disappear automatically if they're not useful anymore (for instance, the I/O error is gone after a while)
add start-up info dialog for vendor-specific auto-sync problems (notably Xiaomi and Huawei)
removed unnecessary permission activity (now handled by account activity)
library updates (including icaj4j 2.2.0 and okhttp 3.10 which should now be able to handle unexpected HTTP 100 status messages)
various other improvements and bug fixes
If you get the "SQLiteException: no such column: metadata_dirty" error message when synchronizing contacts, please have a look at FAQ: SQLiteException: no such column: metadata_dirty
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