Synchronize appointments with caldav and radicale

gpatel-fr

@ubports said in Synchronize appointments with caldav and radicale:

the calendars fail to syncronize

lduboeuf

@ubports said in Synchronize appointments with caldav and radicale:

I'm suffering the same. I have a radicale server and the calendars fail to syncronize with ubports 24.04 stable and fairphone 5. No problems with nextcloud accounts

hmm, i might try again. It was working for me 1 or 2 months ago, but need to check on both 24.04.1.x and 24.04.2.x

gpatel-fr

@lduboeuf said in Synchronize appointments with caldav and radicale:

It was working for me 1 or 2 months ago, but need to check on both 24.04.1.x and 24.04.2.x

did you fix #214 then ? if yes, this is not ported to 24.04-1.1 stable.

gpatel-fr

Err, when creating a distant connection, the distant calendar is not seen in the UI until the sync has succeeded, but once it's done it's possible to select it, even in 24.04.1.1 stable. When thinking of it, it's obvious. My bad.

lduboeuf

said in Synchronize appointments with caldav and radicale:

@ubports said in Synchronize appointments with caldav and radicale:

I'm suffering the same. I have a radicale server and the calendars fail to syncronize with ubports 24.04 stable and fairphone 5. No problems with nextcloud accounts

hmm, i might try again. It was working for me 1 or 2 months ago, but need to check on both 24.04.1.x and 24.04.2.x

Confirmed it works on both 24.04.2x and 24.04.1.x daily, so it is just a matter of time for the stable

lduboeuf

@gpatel-fr said in Synchronize appointments with caldav and radicale:

@lduboeuf said in Synchronize appointments with caldav and radicale:

It was working for me 1 or 2 months ago, but need to check on both 24.04.1.x and 24.04.2.x

did you fix #214 then ? if yes, this is not ported to 24.04-1.1 stable.

No, didn't do anything regarding that, but there was issues with Noble that get fixed meanwhile

gpatel-fr

@lduboeuf

I think that I can as well note here the results of my sunday tests with Radicale and UT, it will allow me to retrieve them easily and maybe be of some usefulness to others: it works with 24.04-1.1 stable, but it can be quirky.

I used a test server that has already other databases, notably an address book, and these database were proposed as options for sync with the calendar.

It's already a problem since an address book is not a calendar.

However it got worse since even after selecting the right database, the sync failed repeatedly until I deleted the 'wrong' databases. The server reported a 400 error on some query aimed to the address book (why oh why since I asked specifically to sync with the calendar...) and the whole sync was failed (I guess that Google Calendar has not this problem since it's just a calendar, it does not try to support all kind of Dav databases like Radicale do)

This was reported by a red indicator in the UI, however the detailed journal was not particularly enlightening, it reported error codes (10400 ? I guess it was error code 400 with database number 10 - so very Unixy error reporting )

The whole testing was not made easier by the syncevolution user interface, a software that has a conception of 'user friendly' that is decidedly selecting its friends. I had to delete the offending files with 'rm' in the evolution (not syncevolution) directory via the command line to get rid of the excess databases in the UI, while they all got back when I deleted the last one (the calendar).
Finally butchering my test server was the right option (and now I don't have any failing test case anymore ).

slowcyclist

@gpatel-fr I also have a Radicale server and UBPorts agenda syncs well with it (both ways) as long as I do not reboot the phone after connecting to the caldav server (i.e. creating the remote caldav account). On subsequent boots, calendars no longer sync; I need to delete the remote caldav account on the phone and recreate it for syncing to work again. It could just be a problem with storing the password (I find it somewhat surprising that once it's created, it's not possible to change the remote account password, AFAICT), but I have not investigated it more than that. And, yes, it's a pain...

lduboeuf

Humm it used to work on 20.04 ?. On 24.04.2 it is broken too but there is a WIP In Lomiri OnlineAccount, don't know for 24.04.1.x

@slowcyclist said:

@gpatel-fr I also have a Radicale server and UBPorts agenda syncs well with it (both ways) as long as I do not reboot the phone after connecting to the caldav server (i.e. creating the remote caldav account). On subsequent boots, calendars no longer sync; I need to delete the remote caldav account on the phone and recreate it for syncing to work again. It could just be a problem with storing the password (I find it somewhat surprising that once it's created, it's not possible to change the remote account password, AFAICT), but I have not investigated it more than that. And, yes, it's a pain...

gpatel-fr

@slowcyclist

err, no, my test reconnects to the server.
However there is something of a strange behaviour that I don't understand currently.
When asking for a sync even in test mode from the command line:

syncevolution --print-databases backend=caldav username=<user> password=<pwd> syncURL=http://192.168.20.12:5232
[INFO] start database search at http://192.168.20.12:5232, from sync config '@default', syncURL='http://192.168.20.12:5232'

I often see a block, the connection is not established (nor refused). After some time (a few minutes ?) the reply is sent. I see the log of the server at the same time, it does not receive anything, it's syncevolution that is refusing to send.
When looking at the same behaviour from the phone UI point of view, when clicking on the sync button, it turns in display busy and after some time the server is receiving data and the sync button turns in mode inactive (but with an red error indicator).
Even trying syncevolution --help blocks.
It's as if syncevolution was refusing to work at some moments.

Looking a bit more, it's as if it's the phone UI connection that is blocking itself (and all other operations such as syncevolution --help or the manual sync that I posted above; when the UI phone attempt at connection finishes, I can then do sync tests from the command line without limitation.

It's as if the sync initiated from the phone UI was blocking syncevolution for about 5 minutes, then it deblocks itself (and other syncevolution clients on the phone such as my test sync) , synchronize the events successfully but returns an error.
A bit of testing seems to show that the delay is about 5-6 minutes. Maybe it's actually that syncevolution is setup to sync every 10 minutes and the button has no effect other than to block until the automatic sync does its thing.

If what you see looks like what I see, that would be a pattern and maybe an issue could be created on Gitlab.