-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SyncKit.CloudKitSynchronizer.SyncError error 0 #144
Comments
Take a look at this Are you triggering a sync before the previous one is finished? |
I sometimes get an error due to which one event is not synchronized ... and no longer when it is not synchronized anymore ... on the phone there is one more event than on the tablet! Can you tell me why this may arise and how to check it? |
I'm sorry, I'm not sure what problem you're trying to describe. Can you provide steps to reproduce and explain the problem with a bit more detail? Can you share code that reproduces the problem? |
Hello, could you please tell me, I have rare cases with a bad Internet when some events are not synchronized. Could you please clarify how I can compare events in the cache with events in realm so that after that call the button eareseLocalMetadata ()? Thank you very much in advance |
It doesn't really work like that. If an operation fails to upload records to CloudKit then it would just fail, and the whole sync would fail. Then you would just retry and next time it would hopefully work. Or, if a single record failed because of a conflict (for example), SyncKit gets the server record, resolves the conflict locally, and still knows that it has to do an upload operation to correctly upload the record. But you don't need to compare events (I'm assuming you mean records) anywhere. |
Hi,
I would like to clarify smth. We’ve got such a mistake on the project.
(SyncKit.CloudKitSynchronizer.SyncError error 0) The operation couldn’t be completed.
What could be the cause of the occurrence?
It would help me a lot.
Thank you in advance!
The text was updated successfully, but these errors were encountered: