[sync-services-developers] Sync Services not taking "no" for an answer?

[Nick Zitzmann]

I noticed recently that my sync client lately has been taking an  
abnormally long amount of time to complete its work, almost as if the  
sync client was performing a slow sync every single time. So I took a  
look at the call history in Syncrospector, and it was performing a  
fast sync, but the sync client was continuously pulling changes that  
the client refused earlier, and these changes are delete changes that  
have not been modified between sessions. Two back-to-back call  
histories show that the sync client rejected the same change twice,  
but Sync Services keeps pushing it.

All that the sync client is doing is:
1. Taking the change obtained from the change enumerator
2. Calling -clientRefusedChangesForRecordWithIdentifier: with the  
sync client's version of the record identifier (which was taken from  
the change from #1)
3. After taking in all changes from all of the change enumerators,  
calling -clientCommittedAcceptedChanges, followed by -finishSyncing

According to the documentation, that should be all, but apparently  
it's not. It doesn't pull committed changes twice, so why is it  
pulling refused changes twice? Has anyone else seen this before, and  
if so, what did you do to get Sync Services to take "no" for an answer?

Nick Zitzmann
<http://www.chronosnet.com/>