Attendees updating their status for 1 instance of a recurring event is triggered as a 'significant change'

[evert]

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[ahackschmitz]

I digged a bit into this and while I'm not 100% certain that this is the same error, I could replicate a problem when a recurring event with exdates gets insignificantly updated (e.g. a new alarm via iCal) and the client changes the order of EXDATE in the ics.

You can find a test in my fork: https://github.com/armin-hackmann/sabre-vobject/commit/4fb6c06a8f1422dd001495095e73f24bc5096284

The ITip Broker simply chains all properties and their values marked to significantly change an event so its pretty obvious why a change is assumed.

We could sort the EXDATE values before adding it (see this commit). I'm not certain if this is the best way to go about it thus 'just' this comment and not a PR. Did I miss something?

[alecpl]

Another case. Server has RRULE:FREQ=WEEKLY;INTERVAL=1, client sends RRULE:FREQ=WEEKLY.