Your TZID does not look right. You must include them in the DTSTART and DTEND lines as follows:
DTSTART;TZID=Pacific/Honolulu:20110628T140000 DTEND;TZID=Pacific/Honolulu:20110628T140000
(Keep in mind: leave āZā at the end of the timestamps if your time is not equal to Zulu time = GMT)
You should add SEQUENCE: xxx, where xxx is the number that increments each time ics is updated. For instance.
SEQUENCE:0
I managed to get this to work (this is bizarre), and it had the same problem as only individual events from my file with several events that were imported. The best trick (mentioned elsewhere) is to get the exported ics file from Google and then clone it.
In the end, I created two separate ics file generators - one for iCal (simple!) And one for Google (hard). Perhaps Outlook needs a third.
Soon you should click on the next problem, which is that Google requires you to specify the time zone for the ICS file and each event that makes coding your application much more difficult. By comparison, Apple iCal allows your ad to post "floating times" that are considered local.
There are a bunch of ics file validation tools you can try, for example, that can be really useful ...
http://icalvalid.cloudapp.net/
Warning. Files that pass this verification tool still do not work with Google. Google really needs to create its own authentication tool.
[waiting to see how many down arrows I get arrows for this message!]
source share