Closed Gewerd-Strauss closed 1 year ago
DTSTART;TZID=/America/New_York:20221117T190000 DTEND;TZID=/America/New_York:20221117T230000
should be
DTSTART;TZID=America/New_York:20221117T190000 DTEND;TZID=America/New_York:20221117T230000
In Helpers.gs after Line 283 add the following to get rid of the "/" at the beginning:
if (tzid[0] == "/"){
tzid = tzid.substr(1)
}
@Gewerd-Strauss - did you have a chance to try @jonas0b1011001 's suggestion?
Closing as there has been no response. Please comment again if this is still an issue
Hello,
I am encountering issues when adding an iCal-calendar containing events from different timezones. The ical-file used during this issue can be found here. For reference, I live in Germany, CEST/GMT+2/GMT+1 (summer/winter).
The Data
Below, you can see the twitch streaming schedule of Critical Role, an USA-based twitch channel. Especially note the time is in the middle of the night, because twitch displays the schedule in your local timezone. Note that in the browser, the time of the next stream is depending on your timezone, and that twitch has correctly established my timezone (GMT+1, we are in winter time here in germany).
This website is a general reference for checking when the next stream occurs depending on your timezone; and on it is stated that CR streams at 7PM pacific. Below you can see that 7-11 PM pacific correlates to 4-8 AM CEST/CET
Now, twitch allows retrieval of the schedule via api, which will return, for this very event, this data:
It is important to know that the timezone of DTSTART and DTEND is NOT relative to the person requesting the API-call. It might be relative to the channel's location, but for that I have not had enough samples I could check yet. I can only assume because it fits in this case, as well as for all the other cases I checked so far (but those are streamers within my own timezone, so its not verifiable yet).
Here is the screenshot of the resulting calendar generated by this script:
And finally, this is the result of adding the ical directly from URL in google calendar, the native way - at the expense of unpredictable updates:
What does this mean?
It seems for a calendar added by this script, the timezone of an event is not taken into account or is not converted to the timezone set in the calendar's settings properly.
To be clear:
Script Settings
The settings are pretty standard:
The timezone of the google script is set to GMt+1 CET - Berlin (just checked and redeployed just in case)
I am happy to give further details wherever possible, and give the ahk-/bash-source code I used for generating the file I am creating the calendar from.
I am aware that it is probably non-standard to have a multitude of different timezones within the same calendar, however when added "the normal way" they are handled fine - and thus I assume this is an issue with the google-script, and not my method of generating the iCal-file.
Thank you.
Sincerely,
~Gw