[Tickets #13847] Re: Duplicated contacts when using ActiveSync on Android

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13847
------------------------------------------------------------------------------
  Ticket             | 13847
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Duplicated contacts when using ActiveSync on Android
  Queue              | Horde Groupware Webmail Edition
  Version            | 5.2.4
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-02-09 23:23) wrote:


> I have only my Sony to test so far. I tried to get an activesync  
> log, but that didn't work for me..
> So i activated the general_log in /etc/mysql/my.cnf and there i can  
> now see the traffic.

This won't help.

> Just for testing, i added an unique key on the table turba_objects,  
> this prevented the dublicates,

There already *is* a primary key on the turba_objects table.

> but the sync never ends.. - that is correct behaviour :-)
>
> Can you tell me, which key is used to get the match between server-  
> and client-Contacts?

object_uid uniquely identifies the contacts.

> Ich have a vcardfile on my mobile with at least 535 contacts that i  
> exported on my device as a backup in nov 2014.
> In Android contacts, i do an import from this file and select the  
> horde exchange account to add the contacts to.. some object_photos  
> are in there too...

This is not supported via ActiveSync, the protocol was not designed  
for large, bulk updates like this from the client. Even with a true  
Exchange server this number of contacts wouldn't work. Unlike the  
server -> client response, there is not "MOREAVAILABLE" tag in client  
-> server requests to split the updates. Most likely your request is  
either timing out or hitting a memory limit. You should instead import  
the vcard file directly via Turba.