1504812 - Google Calendar sync doesn't process recurrency exceptions from Google Calendar anymore

Status: RESOLVED WORKSFORME

(Calendar :: Provider: GData, defect)

Description

[Aron van Ammers]

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce:

Using Lightning Calendar within Thunderbird. Version is reported as 5.4.9.1 (not in list here).

1. Create a recurrent event, for example daily, three occurrences.
2. On Google Calendar on the web (not in Thunderbird), modify one of the occurrences as an exception, for example move the first one one hour earlier.
3. Sync Calendar in Thunderbird


Actual results:

Recurrent event shows without exception. So in the example: the three daily events, all at the same time.

Possibly relevant message in the console (email adapted to "[e-mail]", otherwise unaltered):

[calCachedCalendar] replay action failed: null, uri=googleapi://[e-mail]/?calendar=user%40domain.com, result=item.recurrenceInfo is null, operation=[xpconnect wrapped calIOperation]

Also in the status bar I see: "Syncronizing [e-mail] event N of M", and N always stays lower than M. For example "201 of 204", or "208 of 209".


Expected results:

Recurrent event shows with exception (in the example, the first occurrence one hour earlier.

This has worked correctly for years with this setup. Only recently (some weeks?) it struck me that exceptions didn't come through anymore, so I started debugging.

The issue does not occur when the recurrence exception is set from Thunderbird. In that case, the recurrence exception is shown correctly both in Thunderbird and in Google Calendar. This works no matter on which end the calendar event is created. However if we then modify any of the occurrences on the Google Calendar end and sync, the issue does occur: Thunderbird Calender doesn't show any recurrency exceptions anymore, just the regular recurrency rule (3 daily items on the same time in my example).

Comment 1

[[:MakeMyDay]]

Please check and report back whether this is still an issue with TB 60.3 / Lightning 6.2.3 and Provider for Google 4.4.2 - maybe there is something incompatbile in provider 4.4.2 for Lightning 5.4.x.

Comment 2

[Aron van Ammers]

Just updated to TB 60.3 / Lightning 6.2.3. Provider for Google still 4.4.2. Issue doesn't occur anymore when following repro steps! Can close. Thanks.

Comment 3

[Arthur K. (he/him)]

(In reply to Aron van Ammers from comment #2)

Just updated to TB 60.3 / Lightning 6.2.3. Provider for Google still 4.4.2.
Issue doesn't occur anymore when following repro steps! Can close. Thanks.

Thanks for the follow up. Closing