Shared Calendaring Improvements
 

From the FastMail Blog:

https://blog.fastmail.com/2017/11/04...-improvements/

As usual, Bron does a good job of explaining some pretty technical changes. The addition of Team mode is something that will be welcome. It will be one advantage FastMail has over Google.

I have to say I worry about these changes, since in the past I've had a lot of trouble with large business shared address books that took months to sort out. I have especially bad memories of changes to this during a month of august. Ok if you're in Australia perhaps but in the northern hemisphere it was a real PITA. That's why I would have preferred they didn't do this in the middle of the week. My fingers are crossed :-)

Guys, I am getting a sync error for several hours now. "error during PROPFIND" with Android CalDav-Sync.

It was clear that something would get messed up........:mad:

I starting having the same issue yesterday 07NOV. Android, usingCalDAV-Sync.

org.apache.http.client.ClientProtocolException: error during PROPFIND

As per the article, I removed and re-added my CalDAV settings and I still get this error.

I'm not getting the PROPFIND error but if I do a manual CalDav sync the "Last synced" date does not change. If I do a CardDav sync the date is changed to the date/time of the manual sync. So I added a calendar event using the web interface, did a CalDav sync again and the event did not sync to the phone. So something is messed up.

Same issue
 

Same issue.
Ticket created.



CardDAV-Sync Error:

Could not connect to <myaccount>@fastmail.fm!
Error was:
org.apache.http.client.ClientProtocolException: can't get addressbook info
Please don't report occasional connection errors. Read the article about connection errors instead.

App: org.dmfs.carddav.Sync
App version: 0.4.23
OS version: 24
OS Info: motorola/kinzie_reteu/kinzie:7.0/NPKS25.200-12-4/4:user/release-keys
Manufacturer: motorola
Date: Wed Nov 08 22:34:02 GMT+01:00 2017

CalDAV-Sync Error:

Could not connect to <myaccount>@fastmail.fm!
Error was:
org.apache.http.client.ClientProtocolException: error during PROPFIND
Please don't report occasional connection errors. Read the article about connection errors instead.

App: org.dmfs.caldav.lib
App version: 0.4.32
OS version: 24
OS Info: motorola/kinzie_reteu/kinzie:7.0/NPKS25.200-12-4/4:user/release-keys
Manufacturer: motorola
Date: Wed Nov 08 22:33:40 GMT+01:00 2017

This is ridiculous. Super-fancy "improvements" that have been tested on each and every platform before rollout and what we get is absolutely no sync any more with addressbooks and calendars on the most widely used Android Sync software?!? And instead of going back to a backup of the system and playing with the "improvements" on the beta server, we are asked to wait.....?!? :eek:
This is not what FM was when it was smaller... :-|

It turns out that I AM getting the 'PROPFIND' error. I first tried removing my CalDav account and reinstalling the CalDAV-Sync app. That didn't help. In doing that I noticed that you can turn on error logging, which I did, and that's when I saw the error that you other folks have reported.

I had opened a ticket on the inability to sync and I have updated it to reflect the PROPFIND issue.

So I removed my CalDav account to diagnose this and now have no calendar entries on my phone and no way to restore them. And I suspect there are many others that simply don't know their apps aren't syncing.

https://www.fastmailstatus.com/

A small subset of calendar clients are unable to synchronise. This should be fixed today.

The support is funny, btw... Claims that everything should be fine again and I should check the settings. :D
:mad:

Fix this bug
 

This calendar/contacts syncing issue sucks. I've been a Fastmail users for years, but things like this are making me seriously consider using another provider. Before I came to the forum this morning, I had tried for several hours to sort this out on my own, thinking it was a cal-dav and card-dav issue. Every time I entered a new app password into either app, it set up properly and showed it recognized the Fastmail calendar or contacts. I even tried the suggestion to go manual and add the "/dav" at the end of the URL. No luck.

Now I see that I'm among a small subset of affected users (my wife as well). As one of the earlier posters said, Fastmail should have tested this internally before rolling it out discovering it's buggy.

Both cal-dav and card-dav syncing for me now. Ordinarily, I'd say thanks, but this problem shouldn't have cropped up, should it?

Maybe they made last minute changes and forgot to test them? Because on the foto (https://blog.fastmail.com/assets/2017-11-04/matrix.jpg) of the test, Bron checked "Android apps / Cal/Card DAV sync) as working :)

The photo also indicates "Bron phone". Was one single phone, with one single phone OS version tested? We don't know if the Android OS version was relevant to this problem but it would be interesting to know.

Also, there was a CardDav sync bug occurring at the same time which, unlike the CalDav bug, was not listed on the FastMail system status page.