ROS Release 3.23.6

Changes since 3.23.5:

Enhancements

• Added more detailed error message when a user creation is rejected due to the userId requiring url encoding (only when logging in via JWT). The new message will return both the encoded and non-encoded userId to make it easier to spot the invalid characters.

Fixed

• Fixed an issue that would cause the JWT provider to not replace all invalid characters in a userId. For example, a user with the Id foo|bar|email would result in an error being thrown even if the | character is marked for escaping.

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).