[Tickets #13022] Re: Exceptions to events break ActiveSync synchronization

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13022
------------------------------------------------------------------------------
  Ticket             | 13022
  Updated By         | arjen+horde at de-korte.org
  Summary            | Exceptions to events break ActiveSync synchronization
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2014-03-25 21:13) wrote:

>> Currently I can't explain why some (older) accounts synchronize
>> properly across all devices, but a new account created from scratch
>> won't.
>
> The previous issues with the EAS version mismatch would explain this.

No, not really. This is on a device that uses EAS 14.1 and is also  
happened with Horde_ActiveSync-2.12.4 (so before the regression was  
introduced). With older accounts, I mean Horde accounts, users with  
Horde accounts created years ago (some dating back to 2008).

>> Apparently, the device has the correct timezone (which is what I
>> configured in the Android settings), but events arrive with a
>> different timezone. Could it be there is something wrong with the
>> timezone settings in Kronolith?
>
> No idea. The timezone blob sent to the device looks correct, so I  
> doubt it's a problem with Kronolith or ActiveSync. Unfortunately,  
> since I can't reproduce any of this, you are going to have to tackle  
> this on your own.

I was already afraid you were going to tell me that sooner or later... :-)