920988 - Google CalDAV OAuth2: error with caldav calendar: calendar is empty, but writing suceeds

Status: RESOLVED WORKSFORME

(Calendar :: Provider: CalDAV, defect)

Description

[shopping]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

- use a google calendar using caldav
- tried 'both': old and new URL, like

https://www.google.com/calendar/dav/EMAIL/events

and 

https://apidata.googleusercontent.com/caldav/v2/EMAIL/events

Authentification succeeds in both case. 

Tested on two computer with brandnew Thunderbird v. 24 profile 





Actual results:

- yellow Exclamation mark shown next to calendar (calenadar currently not available)
- no events are shown

BUT: then create a new event: it is NOT shown in lighting, but it is created in the Google calendar correctly (as can be seen in Google Web-Interface)


Expected results:

writing seems to succeed, but reading fails!

Comment 1

[Seth Foss]

Happens to me on Lightning 2.6.3.

Relevant log messages:
[JavaScript Warning: "CalDAV: Error doing webdav sync: 401"]
[JavaScript Warning: "There has been an error reading data for calendar: Days Off Work.  However, this error is believed to be minor, so the program will attempt to continue. Error code: DAV_REPORT_ERROR. Description: There has been an error reading data for calendar: https://apidata.googleusercontent.com/caldav/v2/[redacted]@group.calendar.google.com/events. It has been disabled until it is safe to use it."]
[JavaScript Warning: "There has been an error reading data for calendar: Days Off Work.  However, this error is believed to be minor, so the program will attempt to continue. Error code: READ_FAILED. Description: "]
[JavaScript Error: "[calCachedCalendar] replay action failed: null, uri=https://apidata.googleusercontent.com/caldav/v2/[redacted]@group.calendar.google.com/events, result=2147500037, op=[xpconnect wrapped calIOperation]"]

Comment 2

[Philipp Kewisch [:Fallen][📱📆]]

I believe this was fixed with Lightning 2.6.5, please retest. If it still occurs, feel free to reopen this bug.