Changelog
12.0.0-alpha.2 (2023-04-05)
SyncError.logUrl
which contains the URL to the server log related to the sync error. (#5609)CompensatingWriteError
which indicates that one or more object changes have been reverted by the server.
This can happen when the client creates/updates objects that do not match any subscription, or performs writes on an object it didn't have permission to access. (#5599)Realm.Results#length
) the number of exact matches (with no other query conditions) on a string
/int
/uuid
/objectId
property that has an index. This improvement will be especially noticeable if there are a large number of results returned (duplicate values).date
property that has an index.mixed
property that has an index.bool
property that has an index.mixed
property that does not have an index.THROW_ON_GLOBAL_REALM
which will enable throwing when the app is accessing the Realm
without first importing it from the Realm package.mixed
property with a string operator (contains
/like
/beginswith
/endswith
) or with case insensitivity. ([realm/realm-core#6376](https://github.com/realm/realm-core/issues/6376, since v10.5.0)mixed
property was returning case insensitive matches. For example querying for myIndexedMixed == "Foo"
would incorrectly match on values of "foo"
or "FOO"
. (realm/realm-core#6376, since v10.5.0)mixed
property on a non-empty class/objectType would crash with an assertion. (realm/realm-core#6376, since v10.5.0)Realm.App.Sync#pause()
could hold a reference to the database open after shutting down the sync session, preventing users from being able to delete the Realm. (realm/realm-core#6372, since v11.5.0)Realm.Results
and Realm.List
being in different orders on different devices. Moreover, some cases of the error message Invalid prior_size
may have be fixed too. (realm/realm-core#6191, since v10.15.0)Sync
as named export. #5649App.allUsers
to return a record with the User.id
as the key and the User
as the value. #5671