On Sep 2, 4:53 pm, Dave Riggle <[email protected]> wrote: > > Please don't tell me I'm going to have to pull apart the RRULES I'm > > given, validate and fix them, and then send them to Google. > > I've always had to do that. But worse, it looks like Google has jumped > the gun by adopting RFC 2445bis with respect to requiring the DTSTART > to conform to the RRULE. That has thrown a wrench into my old libical > parser. :(
Hi everyone, Sorry for the delay in responding to this thread. We're aware of this issue, and are currently investigating solutions. Unfortunately, at this time I don't have an ETA for a fix. To be clear: This appears to be caused when the created event contains a gd:recurrence element containing invalid data. For example: lacking an RRULE, or having a DSTART value that is impossible given the provided RRULE. The workaround right now is to make sure that gd:recurrence data is correct. I realize this isn't ideal, and again, we're investigating solutions to this problem. -- Trevor Johns --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
