Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Runtime not ready for debugging" running off real iPhone #7131

Closed
fungilation opened this issue Apr 22, 2016 · 3 comments
Closed

"Runtime not ready for debugging" running off real iPhone #7131

fungilation opened this issue Apr 22, 2016 · 3 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@fungilation
Copy link

I'm getting the redbox "Runtime not ready for debugging" while testing on real device. It's all fine in simulator.

I see on RN's doc that I should update RCTWebSocketExecutor.m from "localhost" to my local server IP. I've already done that in AppDelegate.m and running the package on real device works fine. But there is no RCTWebSocketExecutor.m in my current version of RN! (0.24) Is this a case of file reshuffling from older RN version and the file just doesn't exist anymore? If so, what/where should the IP be configured for debugging from running on a real iOS device?

Thanks for advice, and also RN's doc can use updating too perhaps regarding RCTWebSocketExecutor.m.

PS. Related to #297 but not for simulator, in which case the default localhost works.

@grabbou
Copy link
Contributor

grabbou commented Apr 22, 2016

@alokverma65977
Copy link

alokverma65977 commented Apr 22, 2016

Checkout the Certificates that are installed if You run on the iPhone device.

@ghost ghost closed this as completed in 7192984 Apr 22, 2016
ptmt pushed a commit to ptmt/react-native that referenced this issue May 9, 2016
Summary:Fixes facebook#7131

I believe it's easier if we just link to this file so it's less confusing what to edit actually. I was originally thinking about linking to specific line, but that will be hard to keep in sync.
Closes facebook#7139

Differential Revision: D3212912

Pulled By: mkonicek

fb-gh-sync-id: 4f272d8bc922b273b961707d9ebf18a3efda31be
fbshipit-source-id: 4f272d8bc922b273b961707d9ebf18a3efda31be
zebulgar pushed a commit to nightingale/react-native that referenced this issue Jun 18, 2016
Summary:Fixes facebook#7131

I believe it's easier if we just link to this file so it's less confusing what to edit actually. I was originally thinking about linking to specific line, but that will be hard to keep in sync.
Closes facebook#7139

Differential Revision: D3212912

Pulled By: mkonicek

fb-gh-sync-id: 4f272d8bc922b273b961707d9ebf18a3efda31be
fbshipit-source-id: 4f272d8bc922b273b961707d9ebf18a3efda31be
bubblesunyum pushed a commit to iodine/react-native that referenced this issue Aug 23, 2016
Summary:Fixes facebook#7131

I believe it's easier if we just link to this file so it's less confusing what to edit actually. I was originally thinking about linking to specific line, but that will be hard to keep in sync.
Closes facebook#7139

Differential Revision: D3212912

Pulled By: mkonicek

fb-gh-sync-id: 4f272d8bc922b273b961707d9ebf18a3efda31be
fbshipit-source-id: 4f272d8bc922b273b961707d9ebf18a3efda31be
@PManager1
Copy link

im getting this issue on iphone simulator, how did you guys solved this ?

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants