Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not works with react-native-threads

See original GitHub issue

Goals

Use realm with react-native-threads

Expected Results

realm can be used with react-native-threads

Actual Results

When start an thread with react-native-threads javascript thread bundle file stuck on top screen, and after press cmd + r, application crashes.

Steps to Reproduce

npm install react-native-threads --save react-native link react-native-threads

npm install realm --save react-native link realm

On index.js start a thread of react-native-threads

react-native run-ios

cmd + r the app should be crash or top green bar stucked with Downloading Javascript bundle 100%.

Version of Realm and Tooling

Realm JS SDK Version: 2.13.0
Node or React Native: 0.52.0
Client OS & Version: Mac OSX High Sierra 10.13.5
Which debugger for React Native: none

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

mwricommented, Aug 9, 2020

I close the issue. Once we implement multi-process support, I expect it to work.

I’m not sure closing the issue is on the basis that it will be resolved when X is implemented is really right. Closing it as “not supported” or “won’t fix” would be OK, but if the issue is valid and it is accepted as WILL be supported, or at least is desirable to support it, and it’s on the road map, however tenuously… then surely we are all best served by the issue being open.

1reaction

knethcommented, May 19, 2020

@tastyqbit We have no estimate for when we will have multi-process support.