Tickets :: Comment on [#12741] EAS 14.x and ActiveSync on Android

* Your Email Address
* Spam protection	Enter the letters below: .___.__ . . __..___ [__ \| \\|__\|(__ [__ \| \|__/\| \|.__)\|
Comment	>> Hi! >> >>> Both the device log and the horde synclog show the event being added >>> once. Looks like a bug in your client. >>> >> >> We have the same problem f.e. on these devices: SAMSUNGGTI9300, >> SAMSUNGGTI9082 and SAMSUNGGTI9505. Phps. a Samsung bug? > > The only Samsung device I have is a Galaxy Nexus, which runs on a > "pure" android ROM. This works fine for me with all versions of EAS, > including 14.0 and 14.1. > >>> Perhaps it's related to the fact that the event spans midnight, utc? >> >> I don´t know. The time is okay for the two events on the Handy >> (GMT+2:00). Like it is on H5 (CEST). > > All times are sent as GMT to the device, so my point was that maybe > since the GMT time of the event covers a date transition, this > might be a trigger for the Samsung bug. Obviously just a guess as I > can't look at ht proprietary source code of Samsung's implementation. > >> I can´t believe, we are alone with this problem. There are two >> installations of H5 (on CentOS6 with pear), two different databases, >> same problem with EAS14. > > I don't see this issue on the 8 physical test devices I have, > Outllook 2013, Windows 8 Mail, or any of the numerous third party > clients I have available to test. > > Do all events get doubled? Is there a pattern to those that do, to > those that don't? Without some sort of information like this, it's > unlikely I'll be able to help further since I can't reproduce.
Attachment
Watch this ticket

Saved Queries