Iswift now manual#
Otherwise, the SyncManager.ErrorHandler is still invoked during the manual client reset process. Option, but not the requirement, to define manual reset handler in these interfaces.
See ErrorReportingBlock ( RLMSyncErrorReportingBlock), and ClientResetInfo for more detail.These error reporting blocks are invoked in the event of a RLMSyncErrorClientResetError.Add the RLMSyncConfiguration.manualClientResetHandler property (type RLMSyncErrorReportingBlock).Add a manual callback handler to ClientResetMode.manual -> ClientResetMode.manual(ErrorReportingBlock? = nil).Add two new additional interfaces to define a manual client reset handler:.RLMClientResetAfterBlock, and the 10.25.0 changelog entry. The two new Obj-C recovery modes support client reset callbacks in notifyBeforeResetĪnd notifyAfterResetfor both and įor more detail on client reset callbacks, see ClientResetMode, RLMClientResetBeforeBlock,.recoverUnsyncedChanges(beforeReset: ((Realm) -> Void)? = nil, afterReset: ((Realm, Realm) -> Void)? = nil). The two new swift recovery modes support client reset callbacks.The client reset process will fallback to ClientResetMode.manual if the recovery process fails in.The client reset process will fallback to ClientResetMode.discardUnsyncedChanges if the recovery process fails in.
Iswift now update#
In the case of conflicting updates to the same field, the client update is applied.If an object was deleted on the client, but not the server, then the client delete instruction is applied.If an object has been deleted on the server, but was modified on the client, the delete takes precedence and the update is discarded.Objects created locally that were not synced before client reset, will be integrated.The changes are integrated with the following rules: A recovery process is run locally in anĪttempt to integrate the server state with any local changes from before the
State of the server after a client reset.
0 kommentar(er)
