recordZoneChangeTokensUpdatedBlock isn't called?

Ok, I see...

So I suppose it is only called if it the changes exceed the batch limit... I had the impression from the WWDC presentation that it replaced the orignal completion block completely.

Have you ever found a solution or workaround for this? I'm experiencing the same issue: recordZoneChangeTokensUpdatedBlock isn't called (if may or may not be after 200 record changes, but I don't have that many records to begin with). Right now I'm always passing a nil token to CKFetchRecordZoneChangesOperation and download every single record in the zone.

The recordZoneWithIDChangedBlock block of CKFetchDatabaseChangesOperation does get called every time but the token is not interchangable with the tokens used in CKFetchRecordZoneChangesOperation.

Filed radar 29886880

It turns out you need to use recordZoneFetchCompletionBlock instead of fetchRecordZoneChangesCompletionBlock. I missed the first one when reading the documentation. The change token is indeed in the recordZoneFetchCompletionBlock.

operation.recordZoneFetchCompletionBlock = {
               (zoneID: CKRecordZoneID,
               serverChangeToken: CKServerChangeToken?, 
               clientChangeTokenData: Data?, 
               moreComing: Bool, 
               error: Error?) in
// do something with the token??
}

I am running this block and it never gets called! The recordChangedBlock and fetchRecordZoneChangesCompletionBlock all get called, but not the recordZoneFetchCompletionBlock. I'm going crazy here...