Closed Bug 1137249 Opened 9 years ago Closed 5 years ago

"Error: A promise chain failed to handle a rejection" when trying to discard an event in the alert

Categories

(Calendar :: Provider: GData, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1150571

People

(Reporter: whimboo, Assigned: Fallen)

Details

As requested by Philipp I upgraded to version 1.0.4 today, but I'm still unable to discard events from the popup. When trying to do so, I see the following error. Maybe it's the reason?

Error: A promise chain failed to handle a rejection.
Date: Thu Feb 26 2015 16:08:58 GMT+0100 (CET)
Full Message: TypeError: this.mDeferred is null
Source File: resource://gdata-provider/modules/gdataRequest.jsm
Line: 231
Source Code:
231
Extra notes so I don't forget: Henrik is also getting the 403 forbidden error from bug 1101175. A PATCH request is being made correctly, but maybe I have to detect if the event is organized by someone else and then PATCH just the private extended properties.
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Also for reference, calendar data being sent:

[calGoogleCalendar] Setting Upload Data (application/json; charset=UTF-8):
{"start":{"dateTime":"2015-02-04T17:30:00+01:00","timeZone":"Africa/Algiers"},"end":{"dateTime":"2015-02-04T18:20:00+01:00","timeZone":"Africa/Algiers"},"summary":"Happy Meeting","description":"Talk about interesting stuff","location":"Room with nice view","status":"confirmed","organizer":{"email":"organizer@example.com","displayName":"Very Cool Person"},"attendees":[{"email":"attendee@example.com,"displayName":"Automation Hero","responseStatus":"accepted"}],"reminders":{"overrides":[],"useDefault":true},"extendedProperties":{"private":{"X-MOZ-LASTACK":"2015-02-26T15:08:58Z","X-GOOGLE-SNOOZE-RECUR":"{\"1424881800000000\":\"20150226T151358Z\"}"}},"recurrence":["RRULE:FREQ=WEEKLY;BYDAY=WE"]}
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.