A bug in Realm js version crashes the app when using remote debugger.

[laurisaarni]

Please see the issue realm/realm-js#1711.

Using realm version 2.2.15 fixes the bug.

[billmalarky]

Looks like that may not resolve it.

realm/realm-js#1711 (comment)

[saarnilauri]

@billmalarky In my case, I had a dependency to Realm in my package.json and to react-native-queue when I changed mine and react-native-queue to use 2.2.15 the problem was gone. I'm not sure if the user claiming it did not work had a similar use case.

[juliancorrea]

About this issue, see this: facebook/react-native#11989 (comment)

The commit that solve the problem is: https://github.com/realm/realm-js/pull/1744/files/aed0fa5cd97db9d19b6951815f369ff943d82d20 e was merged on master.

However, there is no release with it, so I've change the file realm/lib/browser/index.js until a new release.

Its necessary change the realm/lib/user.js too, commenting the line 45, because of the problem that happens next: Cannot redefine property: logout' problem.

[billmalarky]

@saarnilauri To be clear, if I explicitly set the realm dependency in package.json to "2.2.15" as in the PR below (I'll increment the patch version directly on master) this should resolve the issue to your knowledge (assuming people nuke node_modules [and yarn lockfile] and rerun yarn or npm install)?

#19

[billmalarky]

Realm is on 2.4.0 now, is this still even an issue?

[xinhash]

Use this adb logcat *:S ReactNative:V ReactNativeJS:V BackgroundTask:V to log and debug

[billmalarky]

Is this still an issue? Realm is on 2.16.1. Can I close this issue?

[saarnilauri]

Fine by me

[billmalarky]

👌