Closed Bug 1791315 Opened 3 years ago Closed 3 years ago

Synchronize does not work with Google Calendar

Categories

(Calendar :: Provider: CalDAV, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: selfsimilar, Unassigned)

Details

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

Steps to reproduce:

Enter a item on a specific date using the Google Calendar add-on on mine or my wife's Win 10 PC using Thunderbird

Actual results:

When look at it on my wife's Thunderbird my entry does not appear using 'synchronize. I have to close and re-open Thunderbird on her machine

When look on my machine her entry does not appear using 'synchronize. I have to close and re-open Thunderbird on my machine

Expected results:

Synchronized should update the calendar on either machine but it doesn't

Component: Untriaged → Provider: CalDAV
Product: Thunderbird → Calendar

The problem still exists

If I understand this correctly, you're using the Google Provider add-on? If so, this should be reported to the developer of that add-on.

Are you still seeing this issue?

Flags: needinfo?(selfsimilar)

Yes - the issue still persists. I cannot find contact details for the Google Calendar provider

Flags: needinfo?(selfsimilar)

OK, you can find links to community support and bug submission in the description for the add-on here: https://addons.thunderbird.net/en-us/thunderbird/addon/provider-for-google-calendar/

If you'd like, you can try adding the calendar without Provider, File -> New Calendar -> select "On the Network" and then in the Username field type in your Google email. This will use the CalDav support instead of Google's proprietary calendar API, it might work better.

Since this is an issue with the add-on, I'm going to close the bug, as we can't directly fix bugs in add-ons.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID

In the latest Thunderbird update that came through today 102.5.0 the problem was solved. Looks like it was a Thunderbird problem not an issue with the addon which was up to date for 1.02.2.0

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