On 14/07/11 14:03, Patrick Ohly wrote:
On Mo, 2011-07-11 at 18:20 +0200, Patrick Ohly wrote:
I have to go back to fixing some other issues elsewhere now. Let me know
when you think that these issues are fixed.
I tried again with today's activesyncd and still get the "Invalid
synchronization key" error in Client::Source::eas_event::testChanges.
Should that be working now?
Hi Patrick,
I now have the tests working and have reproduced this - the problem is
twofold... firstly, our "random" client id assignment was failing when
called twice is quick succession, so the server rejected an add, because
the client id's were the same... this highlighted another issue, which
is that if there is an error in the add, you get a new sync key, but we
don't return it, because we are dropping out, when we see the error. -
this means that the sync keys are invalid from then on. I will let you
know when I have it all working.
Andy
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
