You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that microsoft has made a (spec invalid?) change to their ICS files that get produced when you publish a calendar via ICS.
Running into it here: nextcloud/calendar#5620
And in digging into the ICS files I'm getting from microsoft, it appears they are not producing END:VEVENT tags anymore, when there is more than one event - they do include one for the last event - just none in a long list of BEGIN:VEVENTS.
Additionally, they are not producing a END:VCALENDAR tag.
Strangely, when I drop these ICS files into the validator at iCalendar.org, it says they are valid. But this parser breaks, looking for the missing END tags.
Thoughts?
Anyone else seeing this, or is it somehow specific to my outlook account? This just broke for me in the last week or so - it has worked fine for years until about a week ago - so I'm assuming Microsoft recently made a change....
The text was updated successfully, but these errors were encountered:
It appears that microsoft has made a (spec invalid?) change to their ICS files that get produced when you publish a calendar via ICS.
Running into it here:
nextcloud/calendar#5620
And in digging into the ICS files I'm getting from microsoft, it appears they are not producing END:VEVENT tags anymore, when there is more than one event - they do include one for the last event - just none in a long list of BEGIN:VEVENTS.
Additionally, they are not producing a END:VCALENDAR tag.
Strangely, when I drop these ICS files into the validator at iCalendar.org, it says they are valid. But this parser breaks, looking for the missing END tags.
Thoughts?
Anyone else seeing this, or is it somehow specific to my outlook account? This just broke for me in the last week or so - it has worked fine for years until about a week ago - so I'm assuming Microsoft recently made a change....
The text was updated successfully, but these errors were encountered: