You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a few issues regarding class support in realm-js. We are currently coming up with strategies to better support this in the future. In the meantime, the following fixes have been applied to help avoid crashes and failures.
When creating a class that extends Realm.Object and pushing the instantiated object to a list, a segmentation fault would occur. This has been fixed by a null check and throwing an exception.
Creating an object from an instance of Realm.Object that was manually constructed (detached from Realm) would fail the second time. Now we throw a meaningful exception the first time.
Removed a delay when running in node.js. It could make testing using Jest to fail. (#3608, since v2.0.0)
During integration of a large amount of data from the server, you may get Assertion failed: !fields.has_missing_parent_update(). (realm/realm-core#4497, since v6.0.0)
Fixed queries for constant null across links to an indexed property not returning matches when the link was null. ([#4460]realm/realm-core#4460), since v3.5.0).
Compatibility
Realm Object Server: 3.23.1 or later
APIs are backwards compatible with all previous releases of Realm JavaScript in the 6.x.y series.
File format: generates Realms with format v11 (reads and upgrades file format v5).