Release 3.14.0

Enhancements

• Added two new config parameters - verifyRealmsAtStart and runPrecheckInChildProcess to replace the now deprecated skipVerifyRealmsAtStart and disablePrecheckInChildProc in the SyncService configuration object. The defaults for the new parameters are false, so unless explicitly configured, consistency checks of the partial Realms will not be run on startup. The old parameters will continue to be respected but will be removed in a future version. (#1338)
• Expose SyncServiceConfig.maxFilesInCache to control the max number of files that will be kept in the sync server cache. (#1340)

Fixed

• Clarified the wording around an error that was occasionally being logged at a warn level with a message starting with Internal sync error. The error message now starts with Unable to connect to a Realm and there's a clarification that this is a transient error that the server will recover automatically from. Also, reduced the log level to detail to properly reflect the ephemeral nature of the error. (#1291)

Compatibility

• Server API's are backwards compatible with all previous ROS releases in the 3.x series.
• The server is compatible with all previous SDKs supporting the ROS 3.x series.

Installation & rollback instructions

Please see the Realm Docs for installation, upgrade and rollback instructions.

Notable known issues

• Encrypting existing realm files is not possible. Only fresh deployments with zero state can use realms encryption. We're working on a migration path for existing deployments.
• Server side Realm files do not compact automatically. The standalone commandline tool "realm-vacuum" can be manually executed to compress free space and old history (See https://docs.realm.io/platform/self-hosted/manage/server-side-file-growth#vacuum-utility).