Ask / Submit

Caldav broken in

asked 2015-03-05 15:04:36 +0300

Arie gravatar image

Caldav accounts are completely broken for me on

I use a personal Davical server, with a self-signed certificate, if that matters. This used to work in the previous sailfish version. Well, in fact there were various bugs, but at least events from the server were visible and some local changes were synced.

After the system update there were no events visible. So I tried to recreate the account with exactly the same settings. However, the following happens. After entering the account details, I get a list of available calendars, and I can set the sync interval – so far so good. (To me this proves that the server details and credentials are correct, otherwise you wouldn't be able to see the list of available calendars.) However, after having entered these details it tries to set up the account and then gives the error "Account needs to be updated settings_accounts-cdav_provider" and the calendar account does not work at all. (The calendars are not listed under "Manage calendars".) When I click on the account in the account list, it says "Not signed in Sign in now to update your credentials for this account". Clicking the "Sign in" button, there is an empty password field. Entering the password and clicking "Accept" leads back to the "Not signed in"-screen, so it does not really help.

This is quite frustrating: I was hoping for the system update to improve the still buggy caldav implementation. It is shocking to instead see it being completely broken.

edit retag flag offensive close delete



Same trouble here; filling password and clicking Sign In doesn't seem to contact the CalDav server (according to logs).

anubis ( 2015-03-05 21:19:09 +0300 )edit

I also use Davical, v., and it works fine both ways pre and post Which version of Davical are you on?

kid ( 2015-03-05 21:26:46 +0300 )edit

On server side i use Owncloud 7.0.4.

anubis ( 2015-03-05 21:37:56 +0300 )edit

My Davical is at version 1.1.1.

By the way, my "Server address" setting used to be "https://server.tld/davical/caldav.php/$user/"; without the $user part, sailfish could not list the available calendars. With the new version, it can do so also when leaving out the "$user/" suffix. Either way, it doesn't work after the account setup, as described above. This may not be relevant, but you never know.

Arie ( 2015-03-05 22:05:33 +0300 )edit

In every version of Sailfish OS there were showstoppers in CardDAV/CalDAV ... broken... shifted time. It is 2015 and Jolla is working on a Table but cannot implement a working CalDAV/CardDAV provider and the worst is, they give it a low priority. That realy piss me off.

kmh ( 2015-03-05 23:51:34 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2015-03-06 06:08:13 +0300

pan tau gravatar image

related dup?

edit flag offensive delete publish link more

answered 2015-03-08 16:13:59 +0300

Arie gravatar image

At Chris' suggestion, I captured the log output. The log showed that there was an SSL error. Enabling the "Ignore SSL errors" option during account creation solves the problem.

It would be nice to know what errors are being ignored and why they occur, but for now at least CalDAV works again.

Thanks Chris!

edit flag offensive delete publish link more


Works by CalDAV, but not by CardDAV.

heubergen ( 2015-03-08 21:26:13 +0300 )edit

As mentioned previously, that bug in CardDAV has recently been fixed and the fix will be released in an upcoming update:

chris.adams ( 2015-03-11 03:46:22 +0300 )edit

answered 2016-08-13 16:24:31 +0300

kaktux gravatar image

I got the ""Account needs to be updated settings_accounts-cdav_provider" since last week - clicking on the message opens account settings - opening the account leads to a password question. But typing the right password doesn't help - the error message appears again.

I am using Taalojärvi/ - and the account is for an owncloud provider (to and worked before without flaws - i changed nothing. On the other hand - since this is an external account - meaning not my own installation - i don't know if this occured when owncloud was updated. The version running is 8.2.

Anyone else encountering this problem? It doesn't appear to be fixed for me.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2015-03-05 15:04:36 +0300

Seen: 953 times

Last updated: Aug 13 '16

Related questions