[Tickets #12506] Re: Contacts sync with ActiveSync get duplicates and not sync

noreply at bugs.horde.org noreply at bugs.horde.org
Sat Aug 3 11:22:04 UTC 2013


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

Ticket URL: http://bugs.horde.org/ticket/12506
------------------------------------------------------------------------------
  Ticket             | 12506
  Updated By         | carlos.velasco at nimastelecom.com
  Summary            | Contacts sync with ActiveSync get duplicates and not
                     | sync
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


carlos.velasco at nimastelecom.com (2013-08-03 11:22) wrote:

Tested the patch and it works, it detects duplicates now.
2013-08-03T13:07:54+02:00 INFO: [15950]  
Horde_Core_ActiveSync_Driver::changeMessage(@Contacts@,  ...)
2013-08-03T13:07:54+02:00 ERR: Already Exists

However, when this happens the server doesn't reply anything for these  
entries, no status is replied for them to client (Android).

Later, as the client device does not see any reply for these entries  
it tries to upload them again and again and again... dups detected, of  
course, but this is bad.

Looking at EAS docs maybe a Status 7 should be replied?
http://msdn.microsoft.com/en-us/library/gg675457%28v=exchg.80%29.aspx
===
7
Conflict matching the client and server object.
The client has changed an item for which the conflict policy indicates  
that the server's changes take precedence.
Item
If it is necessary, inform the user that the change they made to the  
item has been overwritten by a server change.
===

On the other hand, it seems interesting that if the Android device  
doesn't see any status reply for some items it behaves like if they  
were not accepted by the server and try again. Maybe this could be  
used for pacing the client uploads.






More information about the bugs mailing list