Set HAS_ATTENDEE_DATA to 0 for exceptions
Bug: 2891708 Change-Id: Ia38214dcb9d72e45c1e481bc93fc6521ea206d0f
This commit is contained in:
parent
3299d4a0d9
commit
1718115cd1
|
@ -786,6 +786,11 @@ public class CalendarSyncAdapter extends AbstractSyncAdapter {
|
|||
cv.put(Events.EVENT_LOCATION, parentCv.getAsString(Events.EVENT_LOCATION));
|
||||
cv.put(Events.VISIBILITY, parentCv.getAsString(Events.VISIBILITY));
|
||||
cv.put(Events.EVENT_TIMEZONE, parentCv.getAsString(Events.EVENT_TIMEZONE));
|
||||
// Exceptions should always have this set to zero, since EAS has no concept of
|
||||
// separate attendee lists for exceptions; if we fail to do this, then the UI will
|
||||
// allow the user to change attendee data, and this change would never get reflected
|
||||
// on the server.
|
||||
cv.put(Events.HAS_ATTENDEE_DATA, 0);
|
||||
|
||||
int allDayEvent = 0;
|
||||
|
||||
|
|
Loading…
Reference in New Issue