Closed Bug 1845319 Opened 2 years ago Closed 2 years ago

Lightning error message in console: "Invalid alarm ... Illegal

Categories

(Calendar :: E-mail based Scheduling (iTIP/iMIP), task)

task

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: git.girish.mattikop, Unassigned)

Details

+++ This bug was initially created as a clone of Bug #1509385 +++

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0

Steps to reproduce:

Thunderbird 60.3.1, Lightning 6.2.3.1.
Tools -> Developer Tools -> Open Console.
Read console messages

Actual results:

window.controllers/Controllers is deprecated. Do not use it for UA detection. blank
GET
https://www.mozilla.org/projects/calendar/caldata/CanadaHolidays.ics
[HTTP/2.0 200 OK 188ms]
Lightning:"Invalid alarm for item: 5b3c08fc-4f6a-4b12-9f16-9d6d777b28db (BEGIN:VALARM

X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:No value for DESCRIPTION pro

perty. Removing entire property:

X-KDE-KCALCORE-ENABLED:TRUE

END:VALARM

) exception: [Exception... "Illegal value'Illegal value' when calling method: [calIAlarm::icalComponent]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: jar:file:///C:/Users/x/AppData/Roaming/Thunderbird/Profiles/o0khn7q2.Default%20User/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D.xpi!/components/calItemModule.js -> resource://calendar/calendar-js/calItemBase.js :: setItemBaseFromICS :: line 868" data: no]" calItemBase.js:871
uncaught exception: 2147942487 calItemBase.js:868:17

Expected results:

no error messages.
Perhaps the problem is because https://www.mozilla.org/projects/calendar/caldata/CanadaHolidays.ics has a line "DESCRIPTION:" but there is no more text on the line so there is a conversion error.

Summary: Lightning error message in console: "Invalid alarm ... Illegal value" perhaps CanadaHolidays.ics → Lightning error message in console: "Invalid alarm ... Illegal
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → MOVED
Group: mail-core-security
Resolution: MOVED → INVALID
You need to log in before you can comment on or make changes to this bug.