Bug 63881 - Google CalDAV: dummy VALARM
Summary: Google CalDAV: dummy VALARM
Status: RESOLVED FIXED
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: CalDAV/CardDAV (show other bugs)
Version: 1.3.99.3
Hardware: Other All
: highest normal
Assignee: Patrick Ohly
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-24 10:45 UTC by Patrick Ohly
Modified: 2014-07-14 12:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Ohly 2013-04-24 10:45:54 UTC
We need to tell Google explicitly that we don't want the default VALARM added to an uploaded event. We can do that by adding a dummy VALARM with ACTION=NONE. Must include a fake TRIGGER. This is what iOS does.
Comment 1 Patrick Ohly 2014-07-14 12:05:43 UTC
See this commit (for 1.4.99.3):

commit 43ab1aba81467bbfa02a85a4ded67e2fa3733e79
Author: Patrick Ohly <patrick.ohly@intel.com>
Date:   Mon Jul 14 04:46:29 2014 -0700

    Google Calendar: remove child hack, improve alarm hack (FDO #63881)
    
    Google recently enhanced support for RECURRENCE-ID, so SyncEvolution
    no longer needs to replace the property when uploading a single
    detached event with RECURRENCE-ID. However, several things are still
    broken in the server, with no workaround in SyncEvolution:
    - Removing individual events gets ignored by the server;
      a full "wipe out server data" might work (untested).
    - When updating the parent event, all child events also get
      updated even though they were included unchanged in the data
      sent by SyncEvolution.
    - The RECURRENCE-ID of a child event of an all-day recurring event
      does not get stored properly.
    - The update hack seems to fail for complex meetings: uploading them
      once and then deleting them seems to make uploading them again
      impossible.
    
    All of these issues were reported to Google and are worked on there,
    so perhaps the situation will improve. In the meantime, syncing with
    Google CalDAV should better be limited to:
    - Downloading a Google calendar in one-way mode.
    - Two-way syncing of simple calendars without complex meeting
      serieses.
    
    While updating the Google workarounds, the alarm hack (sending a
    new event without alarms twice to avoid the automatic server side
    alarm) was simplified. Now the new event gets sent only once with a
    pseudo-alarm.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.