|
|
Sorry, I have to reopen this.
As you can see, the three subsequent requests didn't contain any changes (i.e. no response tag), but the sync-token changed (I've sent the same sync-token with all three requests). That should not happen.
The sync token should not change if there was no change in the collection. In that case the server should return the same token that was sent with the request.
The sync-token should behave like the ctag in that case. Actually, it's the successor of the ctag. It has the same meaning in terms of indicating changes in a collection, just with the extended functionality to get the actual changes.
I was able to reproduce this with a non-public SOGo installation running 2.0.7. Initially the issue has been reported by a user. |
|
|
Can you try this patch?
--- a/SoObjects/SOGo/SOGoGCSFolder.m
+++ b/SoObjects/SOGo/SOGoGCSFolder.m
@@ -1,9 +1,7 @@
/ SOGoGCSFolder.m - this file is part of SOGo
- Copyright (C) 2004-2005 SKYRIX Software AG
-
- Copyright (C) 2006-2012 Inverse inc.
- *
-
- Author: Wolfgang Sourdeau <wsourdeau@inverse.ca>
-
- Copyright (C) 2006-2014 Inverse inc.
-
- This file is free software; you can redistribute it and/or modify
-
it under the terms of the GNU General Public License as published by
@@ -1358,11 +1356,15 @@ static NSArray *childRecordFields = nil;
}
NSZoneFree (NULL, selectors);
+
- /* If we haven't gotten any result to return, let's use the previously
- supplied sync-token */
- if (max == 0)
- newToken = syncToken;
/ If the most recent c_lastmodified is "now", we need to return "now - 1"
in order to make sure during the next sync that every records that might
get added at the same moment are not lost. /
- if (!newToken || newToken == now)
- else if (!newToken || newToken == now)
newToken = now - 1;
newTokenStr = [NSString stringWithFormat: @"%d", newToken];
|
