[Tickets #12056] Re: New Kronolith appt w/no invitees sync to iOS, result in greyed item in iOS Calendar

noreply at bugs.horde.org noreply at bugs.horde.org
Tue Feb 26 19:50:53 UTC 2013


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12056
------------------------------------------------------------------------------
  Ticket             | 12056
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | New Kronolith appt w/no invitees sync to iOS, result in
                     | greyed item in iOS Calendar
  Queue              | Horde Base
  Version            | 5.0.4
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-02-26 19:50) wrote:

I feel like this could benefit from  some more explanation.

If an invite is received on, AND is dealt with completely from the iOS  
device, this should work fine.  The flow is something like this:

1. Device receives request.
2. Device creates a tentative event locally on the client's calendar.
3. User deals with invitation.
4. Device sends the EVENTRESPONSE request to the server.
5. Server parses the response, adds the new event to the user's  
calendar and sends the response email to the organizer.
6. The server then deletes the original request email from the INBOX,  
which triggers a SYNC on the INBOX. THIS IS THE IMPORTANT STEP. This  
is what causes the client to delete the tentative request.
7. Device requests SYNC for INBOX and Calendar, which causes new event  
to be added, and tentative event to be removed, along with the  
original request email.

If you keep the original request email, the tentative event will NEVER  
be removed.  This has nothing to do with the ORGANIZER field. The  
relevant field here is the (optional) MEETING_STATUS field, which we  
now always send thanks to iOS's broken behavior.





More information about the bugs mailing list