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
Nan's wrapper for these functions incorrectly asserts that the property name
argument is a `v8::String`, while it's actually a `v8::Name` (a superclass of
String) and depending on the whim of the optimizer it may be a different
concrete subclass. This resulted in the realm-js-private tests (and some
non-test code) crashing with the error "FATAL ERROR: v8::String::Cast Could not
convert to string" when run with a debug build of the library.
Fortunately the last time this API changed was in node 0.12 so there's no
actual need to use Nan's wrapper.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@ x.x.x Release notes (yyyy-MM-dd)
6
6
### Fixed
7
7
* <How to hit and notice issue? what was the impact?> ([#????](https://github.com/realm/realm-js/issues/????), since v?.?.?)
8
8
* ReactNative for Android no longer uses deprecated methods and can build using Gradle 5.0 and above. ([#1995](https://github.com/realm/realm-js/issues/1995))
9
+
* Fix occasional "FATAL ERROR: v8::String::Cast Could not convert to string" crashes when reading a property from a Realm object. ([#2172](https://github.com/realm/realm-js/pull/2172), since 2.19.0)
0 commit comments