Closed samuelallan72 closed 3 years ago
In some cases, ics2rem produces a REM that isn't valid and can't be parsed by remind. For example:
REM Apr 30 2018 *14 UNTIL Sep 2 2018 *1 UNTIL May 5 2018 MSG ...
Below is an example ical (with personal details redacted) that triggers the double repeat pattern shown above:
BEGIN:VEVENT DTSTART;VALUE=DATE:20180430 DTEND;VALUE=DATE:20180505 RRULE:FREQ=WEEKLY;UNTIL=20180902;INTERVAL=2;BYDAY=MO DTSTAMP:20210307T030603Z UID:REDACTED CREATED:20180402T141541Z DESCRIPTION:this is the description of this event. LAST-MODIFIED:20180827T162602Z LOCATION: SEQUENCE:1 STATUS:CONFIRMED SUMMARY:This is an event TRANSP:TRANSPARENT X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC BEGIN:VALARM ACTION:AUDIO TRIGGER:-PT15H ACKNOWLEDGED:20180819T172819Z ATTACH;VALUE=URI:Basso UID:REDACTED X-APPLE-DEFAULT-ALARM:TRUE X-WR-ALARMUID:REDACTED END:VALARM END:VEVENT
(I'm not sure if the ICAL is technically valid, but this is an ical created by google calendar)
In some cases, ics2rem produces a REM that isn't valid and can't be parsed by remind. For example:
Below is an example ical (with personal details redacted) that triggers the double repeat pattern shown above:
(I'm not sure if the ICAL is technically valid, but this is an ical created by google calendar)