Using .Net API wrapper for Google Calendar API.
- First get primary calendar id
- Get timezone of primary calendar (returns good data, e.g., "America/Los_Angeles")
- Create a calendar event. Set start time and end time. Set timezone.
Dim eStart As New EventDateTime eStart.DateTime = _startAt eStart.TimeZone = GoogleTimeZone Dim eEnd As New EventDateTime eEnd.DateTime = _endAt entry.Start = eStart entry.End = eEnd eEnd.TimeZone = GoogleTimeZone CalService.Events.Insert(entry, calendarid).Execute()
But the events are being created at 3am when the start time specified is 11am.
Google API documentation states "A time zone offset is required unless a time zone is explicitly specified in timeZone" and for timezone "The time zone in which the time is specified. (Formatted as an IANA Time Zone Database name, e.g. "Europe/Zurich".)".
Timezone value is being specified properly.
Basically, it is not making any difference whether or not timezone is specified. Event is created in GMT in google calendar. What is wrong here?
I fixed it by creating an instance of a DateTime object that uses the
DateTimeKind
enum as one of the constructors. I found the defaultDateTime.Kind
property value isDateTimeKind.Utc
when deserializing a JSON date. That's why a Z (UTC) value is in the Raw for me. The time zone value will be correct when DateTimeKind.Local is applied to the DateTimeKind argument in one of the constructors that takes it.Fixed it (or let's just say hacked it). Google .Net API wrappers are absolutely crap (and this goes to wrapper of all of their APIs and not just Calendar API).
The issue was that
event.Start
andevent.End
automatically converts dates and add a "Z" at the end. This tells Google that the date is in GMT format. There is no reason for putting a "Z" because even without it, Google considers GMT. So basically,event.TimeZone=value
was being disregarded because the time was appended by "Z".After I removed the "Z", everything worked ok.