Realm Xamarin v4.3.0 Release Notes
Release Date: 2020-02-05 // about 4 years ago-
β¨ Enhancements
- π¦ Exposed an API to configure the
userId
andisAdmin
of a user when creating credentials viaCredentials.CustomRefreshToken
. Previously these values would be inferred from the JWT itself but as there's no way to enforce the server configuration over which fields in the JWT payload represent theuserId
and theisAdmin
field, it is now up to the consumer to determine the values for these. - π Improved logging and error handling for SSL issues on Apple platforms.
π Fixed
- Realm objects can now be correctly serialized with
System.Runtime.Serialization.Formatters
andSystem.Xml.Serialization
serializers. (Issue #1913)
The private state fields of the class have been decorated with[NonSerialized]
and[XmlIgnore]
attributes so that eager opt-out
serializers do not attempt to serialize fields such asRealm
andObjectSchema
which contain handles to unmanaged data. - π Fixed an issue that would result in a compile error when
[Required]
is applied onIList<string>
property. (Contributed by braudabaugh) - π Fixed an issue that prevented projects that include the Realm NuGet package from being debugged. (PR #1927)
- π The sync client would fail to reconnect after failing to integrate a changeset. The bug would lead to further corruption of the clientβs Realm file. (since 3.0.0).
- π The string-based query parser (
results.Filter(...)
) used to need theclass_
prefix for class names when querying over backlink properties. This has been fixed so that only the publicObjectSchema
name is necessary. For example,@links.class_Person.Siblings
becomes@links.Person.Siblings
. - π Fixed an issue where
ClientResyncMode.DiscardLocalRealm
wouldn't reset the schema.
Compatibility
- Realm Object Server: 3.23.1 or later.
Internal
- β¬οΈ Upgraded Sync from 4.7.5 to 4.9.5 and Core from 5.23.3 to 5.23.8.
- π¦ Exposed an API to configure the