Closed Bug 1795862 Opened 2 years ago Closed 1 year ago

Thunderbird 102.1.0 and further versions can't create iCloud CalDav calendar

Categories

(Calendar :: Provider: CalDAV, defect)

Thunderbird 102
Unspecified
macOS
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: de.berberich, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Steps to reproduce:
Open Calendar tab, go to File > New > Calendar, choose "On the Network".
Fill in username and Location (URL) of the iCloud calendar which would be something like
https://pXX-caldav.icloud.com/1234567890/calendars/home/
Click "Find Calendars".

Actual results:
Nothing happens, the turning blue circle may turn for hours, Thunderbird doesn't find the calendar.
This happens since version 102.1.0 and following.

Expected results:
Thunderbird should create the CalDav calendar.

This issue still exists in v102.4.0

Anything in error console?

Component: Untriaged → Account Manager
Flags: needinfo?(de.berberich)

Here is a screen shot of the error console after failure to create the CalDav calendar.

Flags: needinfo?(de.berberich)

Possibly bug 1793757

Component: Account Manager → Provider: CalDAV
Product: Thunderbird → Calendar

(In reply to Magnus Melin [:mkmelin] from comment #4)

Possibly bug 1793757

Not sure.
The issue I describe does not occur in versions 91.*, 102.0, 102.0.1, 102.0.2 nor 102.0.3.
First version where it occurs is TB 102.1.0.

Bug 1798231 is reporting another issue, but could apparently set it up fine.

Seems like libc.dylib is missing or not working and so DNS fails here?

Currently running v102.7.2 and having a similar issue. The iCloud calendar I use is able to pull events created in Thunderbird, but not able to push events created in iCloud (through phone, browser, etc) back to Thunderbird.

What does this tell us exactly, that the app-specific password and caldav URL is correct but Apple has issues on it's end for incorrect authentication perhaps?

Blocks: tb-mac
No longer blocks: tb-mac
Blocks: tb-mac

I can confirm that synchronising with or re-creating a new calendar via caldav at my posteo.de account which I had been using flawlessly for several years doesn't work anymore in TB 102.1 (v102.11 on Arch Linux here). Here's what the error console reports:

12:54:28.513 Calendar: [CalICSProvider] Could not detect calendar using method attemptHead - HTTP response status -1 CalICSProvider.jsm:94
12:54:28.520 Calendar: [CalICSProvider] Could not detect calendar using method attemptGet - HTTP response status -1 CalICSProvider.jsm:94
12:54:28.527 Calendar: [CalICSProvider] Could not detect calendar using method attemptDAVLocation - HTTP response status -1 CalICSProvider.jsm:94
12:54:28.539 Calendar: [CalICSProvider] Could not detect calendar using method attemptPut - HTTP response status -1 CalICSProvider.jsm:94
12:54:28.539 Calendar: [CalDavProvider] Could not detect calendar using method attemptLocation - HTTP response status -1 CalDavProvider.jsm:99
12:54:28.546 Calendar: [CalDavProvider] Could not detect calendar using method wellKnown - HTTP response status -1 CalDavProvider.jsm:99
12:54:28.552 Calendar: [CalDavProvider] Could not detect calendar using method attemptRoot - HTTP response status -1 CalDavProvider.jsm:99
12:54:28.552 Calendar: Error during calendar detection: resource:///modules/calendar/utils/calProviderDetectionUtils.jsm:20: NoneFoundError
DetectionError@resource:///modules/calendar/utils/calProviderDetectionUtils.jsm:20:1
@resource:///modules/calendar/utils/calProviderDetectionUtils.jsm:31:7
detect@resource:///modules/calendar/utils/calProviderDetectionUtils.jsm:164:26

Again, this had worked in the past without any problems. I also add that my iPhone and the KDE app KOrganizer still work flawlessly. It's obvious that something is broken in Thunderbird.

(In reply to circularsol from comment #8)

What does this tell us exactly, that the app-specific password and caldav URL is correct but Apple has issues on it's end for incorrect authentication perhaps?

It's not an Apple issue since CalDav for iCloud works fine until TB 102.0.3 !
Beginning with TB 102.1.0 you can no longer create an iCloud CalDav calendar. Very odd :from one minor version to the next minor version it stops working.
A workaround: install TB 102.0.3 (or earlier), create your iCloud CalDav calendars, then update to the actual version.
Once installed in TB 102.0.3 your calendars will continue to work flawlessly after each update to a more recent version.

It's not an Apple issue since CalDav for iCloud works fine until TB 102.0.3 !

As mentioned in my post, the problem not only applies to caldav with iCloud. My calendars at posteo.de and mailbox.org aren't accessible anymore, either. They continue to work with my iPhone and with Korganizer. This is a general problem concerning caldav with Thunderbird.

(In reply to Magnus Melin [:mkmelin] from comment #11)

Not many changes for that - https://hg.mozilla.org/releases/comm-esr102/pushloghtml?fromchange=THUNDERBIRD_102_0_3_RELEASE&tochange=THUNDERBIRD_102_1_0_RELEASE

Is there any chance this could be a knock-on effect from an m-c change?

Anything is possible.

(In reply to Thomas Ludwig from comment #12)

As mentioned in my post, the problem not only applies to caldav with iCloud. My calendars at posteo.de and mailbox.org aren't accessible anymore, either.

You may be experiencing some other issue, possibly with 3rd party software such as antivirus/firewall.
My mailbox.org calendar seems to work just fine.

Okay, I created a new profile and could successfully add a caldav calandar. So I went back to my normal profile, deactivated tentatively uBlock Origin - and success, success: it worked! I have no idea why uBlock Origin (configured to use Dynamic Filtering in Hard Mode - see https://github.com/gorhill/uBlock/wiki/Blocking-mode:-hard-mode) would interfere with the calendar but it obviously did.

Comment on attachment 9354715 [details]
caldav-icloud-thunderbird.png

With 102.15.1 I am getting this error:
"Could not find calendars at this location. Please check your settings."

Is that because of this bug?

(In reply to Sledge Hammer from comment #17)

Is that because of this bug?

Exactly, YES !

Eventually this bug has been fixed in version TB 115!

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED

We use fixed only when a known patch resolved the issue.

Resolution: FIXED → WORKSFORME

Thanks, Magnus!

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: