ClientResetHandler is triggered if the device and server cannot agree
on a common shared history for the realm file
or when it is impossible for the device to upload or receive any changes.
This can happen if the server is rolled back or restored from backup.
A client reset strategy that attempts to automatically recover any unsynchronized changes.
If that fails, this handler fallsback to the discard unsynced changes strategy.
An object encapsulating a synchronization session. Sessions represent the
communication between the client (and a local Realm file on disk), and the
server. Sessions are always created by the SDK and vended out through various
APIs. The lifespans of sessions associated with Realms are managed automatically.
A class representing a single query subscription. The server will continuously
evaluate the query that the app subscribed to and will send data
that matches it as well as remove data that no longer does.
Thrown when an error occurs during synchronization
This error or its subclasses will be returned to users through FlexibleSyncConfiguration.syncErrorHandler
and the exact reason must be found in the message.