SyncServerDelegate

The client has to decide how to resolve the content-download conflicts. The resolveConflict method of the SyncServerConflict must be called. The statements below apply for the SMRelativeLocalURL’s.

Not called on the main thread. You must call the conflict resolution callbacks on the same thread as this was called on.

The syncServerFileGroupDownloadComplete method will be called after, if you allow the download to continue. i.e., if you use acceptContentDownload of ContentDownloadResolution.

The client has to decide how to resolve the download-deletion conflicts. The resolveConflict method of each DownloadDeletionConflict.uploadConflict must be called.

Conflicts will not include UploadDeletion.

Not called on the main thread. You must call the conflict resolution callbacks on the same thread as this was called on.

The number of elements in this array reflects the number of conflicts in the download deletions. E.g., if there is only a single download deletion, there can be at most one conflict.

Called at the end of a group download, on non-error conditions, after resolution of conflicts.

For file downloads, the client owns the file referenced by the url after this call completes. This file is temporary in the sense that it will not be backed up to iCloud, could be removed when the device or app is restarted, and should be copied and/or moved to a more permanent location. Client should replace their existing data with that from the given file.

This method doesn’t get called for a particular download if (a) there is a conflict and (b) the client resolves that conflict by using .rejectContentDownload

The operation is appMetaData if the app meta data on the server was updated without a corresponding file content change.

For deletion operations, clients should delete the files referenced by the SyncAttributes’s (i.e., the UUID’s).

For files you upload without file groups, this callback always has a single element in the array passed.

Like the above, but at least one of the file downloads could not be completed because the file was gone on the server. See the group info for details. It is up to the client app to inform the user and re-attempt downloads of files that are gone, if wanted. See the reAttemptGoneDownloads option of the sync method.

Called when sharing group operations occur because of downloads (i.e., changes by other users). updated has the specific meaning that SyncServer updateSharingGroup was performed by another app. syncNeeded in sharing groups will be nil.

Reports events. Useful for testing and UI.