IssueTracker

Description

When you send someone an iCal attachment with the event information and the method is PUBLISH, when the recipient opens the email in Gmail, they are then presented with the option to create that event in their calendar. However when the event in the calendar is created, the UID sent with the iCal attachment is discarded and Google generates a new UID in its place.

From iCal RFC2446 you should be able to publish an event with the method:PUBLISH and then later update the same event with another method:PUBLISH call. This is however not possible since the UID is changed and when you send a new method:PUBLISH to update the event, the event UID would not match and an option to create a new one is shown instead.

This also disables any flows that use PUBLISH -> CANCEL

Steps to reproduce

• Send someone an iCal attachment with some event information using the method:PUBLISH
• Open that email in Gmail and click the "Add to calendar button"
• Send another iCal attachment to update to the event using method:PUBLISH(can also use method:CANCEL) and the same UID
• The option to add a new event is presented instead of updating the existing event
• To verify, after adding the event to your calendar, you can export the calendar and see in the iCal file that the UID for that event has changed.

Expected behaviour

• After adding the event to calendar from Gmail, the UID from the iCal attachment should be preserved
• When sending another PUBLISH/CANCEL iCal attachment with the same UID, the event should update/be removed as defined in the spec.