You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to implement an app with sync between iOS and macOS.
Now I'm at the pint where a notofication from CloudKit should trigger the sync. On iOS everything works fine, but not on macOS. If I start the sync process with synchronizer?.synchronize(completion: ((Error?) -> ()) I got a "CloudKitSynchronizer >> Initiating synchronization" print on the console and a following SyncError without any further information.
I think this error raises because of an empty zoneID in line 35 of the following code.
SyncError is an Int enum, do you know which case you're getting?
For reference:
@objcpublicenumSyncError:Int,Error{
/**
* Received when synchronize is called while there was an ongoing synchronization.
*/
case alreadySyncing =0
/**
* A synchronizer with a higer `compatibilityVersion` value uploaded changes to CloudKit, so those changes won't be imported here.
* This error can be detected to prompt the user to update the app to a newer version.
*/
case higherModelVersionFound =1
/**
* A record fot the provided object was not found, so the object cannot be shared on CloudKit.
*/
case recordNotFound =2
/**
* Synchronization was manually cancelled.
*/
case cancelled =3}
I'm trying to implement an app with sync between iOS and macOS.
Now I'm at the pint where a notofication from CloudKit should trigger the sync. On iOS everything works fine, but not on macOS. If I start the sync process with
synchronizer?.synchronize(completion: ((Error?) -> ())
I got a"CloudKitSynchronizer >> Initiating synchronization"
print on the console and a followingSyncError
without any further information.I think this error raises because of an empty
zoneID
in line 35 of the following code.SyncKit/SyncKit/Classes/QSSynchronizer/Operations/FetchDatabaseChangesOperation.swift
Lines 28 to 55 in 1a1c040
@mentrena it would be really cool if you could have a look at this.
The text was updated successfully, but these errors were encountered: