Error Domain=QSCloudKitSynchronizerErrorDomain Code=0 "(null)" about synckit

[spotlessicode]

1. Sync completion Block

I have found, that you call completionBlock, just if error isn't nil
So I tried, in QSCloudKitSynchronizer.m
- (void)finishSynchronizationWithError:(NSError *)error
after
QSCloudKitSynchronizerDidSynchronizeNotification
I added:
NSError *error2 = nil;
callBlockIfNotNil(self.completion, error2);

and at my App side in AppDeleagte.m
[self.synchronizer synchronizeWithCompletion:^(NSError *error) {

if((!error)||([error isEqual:[NSNull null]])){ NSLog(@"No error"); }else{ NSLog(@"error snyc end: %@", [error localizedDescription]); }

2. Table update /FRC update after sync
At the table update.. IT doesn't work after I commented out sync after creating object.. But at a clean start without any data, it works, until I call first time the self.synchronizer synchronizeWithCompletion strange. I test it more.

3. QSCloudKitSynchronizerErrorDomain Code=0
Int he last 2 hours there were nor Error Domain=QSCloudKitSynchronizerErrorDomain Code=0 "(null)" errors. But if you know, when it's happening/the meaning, please let me know.

[spotlessicode]

1. Sync Completion Block

• should I check if sync ends, for subscribing with ZONEID data changes, so the device B will know, if it changed? (Or based on your wiki, we shouldn't).
• any other mode to be notified, if sync ends?

2. FRC
(NSFetchedResultCotnroller can't see the objects if I start sync after save and unwind)
I couldn't solve this problem in the last hours.. everything is perfect without synchronization.

3. QSCloudKitSynchronizerErrorDomain Code=0
I have again this issue but just sometimes..(when it comes, sync doesn't run, so FRC works) What causes this? could it be a poor internet connection? or what else? How could we get more error info?

[mentrena]

Hi,

I'm trying to understand the problem, let's see.

QSCloudKitSynchronizerErrorDomain Code=0

I believe that's QSCloudKitSynchronizerErrorAlreadySyncing (definition in QSCloudKitSynchonizer.h)
Which means that your app is already in the process of synchronising data with CloudKit.
The first caller of synchronizeWithCompletion will have its completion block called when sync finishes. Successive callers will immediately receive the "already syncing" error.

So yes, it could be due to a poor connection.
Could you clarify these two things:

• The first time you call synchronizeWithCompletion you don't get that error./
• After you call it a second time and you get the error, can you confirm that the synchroniser is still trying to sync? (by pausing with the debugger, or looking at the debug lines being printed)

[spotlessicode]

Hi, I’m not sure about the poor connection, but I tried clean all sync and run just once in the whole App, and sometimes get that issue on physical device sometimes not. I checked the table problem too, just happening when sync starts after MOC saved. I want to test it more deeply this issue, but because on a trip I can first on Monday. I’ll let you know! Thanks!

…

----------------------------- Eva Puskas

-----------------------------

Am 22.11.2018 um 19:40 schrieb Manuel Entrena ***@***.***>: Hi, I'm trying to understand the problem, let's see. QSCloudKitSynchronizerErrorDomain Code=0 I believe that's QSCloudKitSynchronizerErrorAlreadySyncing (definition in QSCloudKitSynchonizer.h) Which means that your app is already in the process of synchronising data with CloudKit. The first caller of synchronizeWithCompletion will have its completion block called when sync finishes. Successive callers will immediately receive the "already syncing" error. So yes, it could be due to a poor connection. Could you clarify these two things: The first time you call synchronizeWithCompletion you don't get that error./ After you call it a second time and you get the error, can you confirm that the synchroniser is still trying to sync? (by pausing with the debugger, or looking at the debug lines being printed) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.