Read the statement by Michael Teeuw here.
TypeError: curr.start.toISOString is not a function
-
Ok, preliminary digging done. It appears the pattern matching isn’t working correctly for the times that Office386 puts on its calendar, I mean, really 1601 for a year? I don’t think so.
Anyway, I’m going to tag @MichMich on this since he wrote the default calendar and I believe the node-ical stuff as well. I have the output of the ICS, so if you had shared it to get me the link, you can unshare it. I can work with the saved output.
-
ok, sounds not that good as expected. Whats next?
-
Basically one of us has to find the time to investigate. The way Office386 creates its dates is really odd. Leave it to Microsoft to break things … as always.
-
ok, my girlfriends calnedar is working. also with office 365 :-) so stupid…
-
Does she have the same events as you? Setup the same way? Same time zones configured?
-
she has different events in her calendar, but the all the other things are the same as mine.
-
Do you have a calendar feed which I can test that gives the error?
-
please give me your Mailadress, I’ll share my Calendar with you. :-)
-
Got it. Thanks. Will probably be able to look into this next week. Is that ok?
-
yeah, no problem. today my calendar is running. I’ve made no changes…
strange, I’ve sent you the link to the working one.
Thanks! :hand_splayed_tone1:
