CREATED, DTSTAMP, LAST-MODIFIED not stored as UTC about calendar HOT 3 CLOSED

Hi, I opened #561 last summer 🙂. I'm migrating to NC12 and smacked into this again. Are we mostly just waiting for kewisch/ical.js#260 to move?

I did find this block in icalFactory.js, which looks relevant:

		event.updatePropertyWithValue('created', ICAL.Time.now());
		event.updatePropertyWithValue('dtstamp', ICAL.Time.now());
		event.updatePropertyWithValue('last-modified', ICAL.Time.now());
		event.updatePropertyWithValue('uid', uid);

		//add a dummy dtstart, so it's a valid ics
		event.updatePropertyWithValue('dtstart', ICAL.Time.now());

Would it be completely, totally irrational to do something like this instead? 😇

                tstamp = ICAL.Time.now() + "Z"
		event.updatePropertyWithValue('created', tstamp);
		event.updatePropertyWithValue('dtstamp', tstamp);
		event.updatePropertyWithValue('last-modified', tstamp);
		event.updatePropertyWithValue('uid', uid);
		event.updatePropertyWithValue('dtstart', tstamp);

Or maybe there's already proper js to do?:

                tstamp = Time.ToUTC(ICAL.Time.now())
                ...

from calendar.

This issue prevents a user at mail.com from subscribing to an iCalendar hosted on Nextcloud. I verified this by manually adding 'Z' after each date-time. Since NC is non RFC compliant, could this be bumped, please.

from calendar.

I have a similar issue, where even a time zone ID is specified in DTSTAMP, which fails e.g. other iCal parsers (ical4j/ical4j#303).

The affected calendar events are not created using the calendar app but have been imported. Is there a way that existing entries could be validated (or that editing them fixes the issue)?

from calendar.