React-native: debuggerWorker.js:18Uncaught NetworkError: Failed to execute 'importScripts' on 'WorkerGlobalScope' Error

[dazziola]

After much frustration and testing potential edge cases, I finally have some form of a debug connection between my computer and my physical device when running a basic (the init code) React Native app on an iPhone through XCode. I am unable to get a debug bridge or a hot reload workflow up and running. I can get these scenarios working on my work computer but not at home.

The connection is picked up by my http://localhost:8081/debugger-ui window, however React Packager does not establish a connection with a client. I am left with an uncaught network exception for _main.jsbundle_

These problems are as a result of running react-native init testApp so no code modification have yet been made.

I can get around this error by disabling remote debugging, but that negates the usefulness of the tooling supplied by React Native in my opinion.

In the interest of brevity, the hot reloading and JS debug bridge does work in the virtual Simulator on the computer. I have also tried to change the IP address in RCTWebSocketExecutor.m to my computers local address. This alleviated prior issues (namely: Runtime is not ready for debugging and WebSocket Connection failed Code=61 errors).

Hopefully someone has come across these problems.

My environment is:
Mac OSX 10.11.6
Node: 5.11.1
React-native: 0.30.0

[charpeni]

@facebook-github-bot label Icebox

[charpeni]

Hi there! This issue is being closed because it has been inactive for a while.

But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/debuggerworkerjs18uncaught-networkerror-failed-to-execute-importscripts-on-workerglobalscope-error

ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.

Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.

[charpeni]

@facebook-github-bot close

[facebook-github-bot]

@charpeni tells me to close this issue. If you think it should still be opened let us know why.

[farooqmajeed]

kindly any one tell how to solve this issue

[wolverineks]

try disabling debugger, sometimes it masks the real error

[lionbur]

@wolverineks Yes, it worked for me (stopping debugging revealed the real error)

[futurechallenger]

@wolverineks It worked for me too. Just close the debugger page!