[Syncevolution-issues] [Bug 5635] test and support Memotoo

Thomas, A new issue is raised. When server alerts a '200' two-way sync, the server misses a 'Last' element, which is used to be compared for the use of anchor matching. I could confirm that this issue didn't occur on Sep 10th. It should be a new bug in recent days. Thomas, could you help check it please? The part of the server incoming SyncML message: <Alert> <CmdID>6</CmdID> <Data>200</Data> <Item> <Target> <LocURI>./vcard21</LocURI> </Target> <Source> <LocURI>con</LocURI> </Source> <Meta> <Anchor> ---> should have a child "<Last>" element to make anchors matched with last sync <Next>1253195512000</Next> </Anchor> <MaxObjSize>1000000</MaxObjSize> </Meta> </Item> </Alert> Below is the subpart of a server SyncML message before Sep 10th. <Alert> <CmdID>6</CmdID> <Data>200</Data> <Item> <Target> <LocURI>./vcard21</LocURI> </Target> <Source><LocURI>con</LocURI></Source> <Meta> <Anchor xmlns='syncml:metinf'> <Last>20090904T075939Z</Last> --- Here is the 'Last' anchor element <Next>20090904T075943Z</Next> </Anchor></Meta></Item></Alert>