react-native-threads: iOS Error
Android seems to work, but when I run iOS, I see:
2017-10-06 15:21:28.391 [fatal][tid:com.facebook.react.WebSocketExecutor] Runtime is not ready for debugging. Make sure Packager server is running.
I’m not manually running a second packager, do I need to?
About this issue
- Original URL
- State: open
- Created 7 years ago
- Reactions: 5
- Comments: 22 (7 by maintainers)
Same here
Are there any news on this? This is still an issue for me
@VertaZoom Unfortunately you cannot have the remote debugger turned on while using react-native-threads. If you have turned on the remote debugger and run into this problem you will need to disable remote debugging from the development menu, and then you’ll need to stop and restart the app by double pressing the home button and swiping it away. I currently recommend using a debugging tool like reactotron to work around this issue. See the example app in this repo for a reference on how to set that up, it is pretty simple to configure.
I’m hoping to find time soon to see if I can get better support for the built-in remote debugger working
@garrettm sorry to hear that, I would definitely recommend using the latest release of react-native-threads as we’re working out the bugs.
Unfortunately right now running the remote debugger will cause crashes and I still need to research how to either stop the debugger from launching for the background thread, or get the debugger to support threads. I don’t really know much more than you do at this point about how to do that.
For now my recommendation is to not run the remote debugger and instead use tools like Reactotron. Check out the example app to see the recommended debugging workflow.
I’ll keep looking into this and keep you updated when I figure out how to make the remote debugger behave better.