Comment 3 for bug 1626235

I had this bug as well and decided to take a peek at the code. My two cents:
- the event is registered with the correct datetime: e.g. I'm in a GMT+8 timezone and 15 dec 2016, 22.00 is stored with an iCalDateTime of 20161215T140000Z.
- when the event is read back, the ical_to_date_time() method in Utils.vala stores it in a DateTime object. From other usages in the code it seems that the app expects this to be a local DateTime which it is not.
- ical_to_date_time() should probably return the .to_local() version of the DateTime object it just created (quickly checked this and it seems to show the correct representation).