[Tickets #14255] Re: Shared calendar Android 6 - /POOMCAL:Exception

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14255
------------------------------------------------------------------------------
  Ticket             | 14255
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Shared calendar Android 6 - /POOMCAL:Exception
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2016-02-15 14:47) wrote:

>> Spent the last 2 hours trying to get the Android 6 emulator to sync
>> the calendar at all. Going to have to give up on this for now, until
>> I can get my hands on a physical Android 6 device.
> Something i can do?

Thanks for the offer, but at this point I'm not sure. I need to be  
able to trace the code while it's syncing to see what is causing this.  
I'm pretty sure 6.0.0 is badly broken with respect to EAS but the  
6.0.1 update isn't available for the emulator yet.

That being said, I'm having a hard time figuring out how the Android  
version would cause the data being sent FROM the server to be corrupt.  
Maybe a few questions:

You said it was a shared calendar.  Does the same thing happen with a  
similar recurring event on your personal calendar? Does the event  
actually have any exceptions? If so, are they changes to an event or  
was the instance removed? Were the exceptions created by the calendar  
owner, or another user?