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

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/10731
------------------------------------------------------------------------------
  Ticket           | 10731
  Aktualisiert Von | joniw at t-online.de
  Zusammenfassung  | Duplicated contacts when using ActiveSync on Android
  Warteschlange    | Synchronization
  Version          | Git master
  Typ              | Bug
  Status           | Assigned
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


joniw at t-online.de (2011-11-09 20:00) hat geschrieben:

> Ah. I misread your original post. The s from an incoming change  
> only. All the other clients I've tested seem to send a getchanges  
> with all incoming sync requests. We'll have to not save a *new*  
> timestamp here, but rather persist the existing one.

But if you keep the existing timestamp would not the updated contact  
be duplicated on the next sync with the same device?

> I'll look at this next time I'm in front of my computer.

Thank you!