Does this not work with Chrome debugging?
seantempesta opened this issue · 9 comments
So I've got the example up and running, but it crashes if I enable Remote JS Debugging:
2016-08-01 17:00:33.792 WorkerSampleApp[3333:62924] starting Worker http://localhost:8081/simple-worker.bundle?platform=ios&dev=true&minify=false
2016-08-01 17:00:33.934 [info][tid:NSOperationQueue 0x7f9633f18bd0 :: NSOperation 0x7f9633c1d220 (QOS: LEGACY)][RCTPerformanceLogger.m:41] Unbalanced calls start/end for tag 0
2016-08-01 17:00:35.791 [fatal][tid:com.facebook.react.WebSocketExecutor] Runtime is not ready for debugging. Make sure Packager server is running.
2016-08-01 17:00:35.830 [error][tid:com.facebook.react.RCTBridgeQueue][RCTWebSocketExecutor.m:78] Connection to http://localhost:8081/debugger-proxy?role=client timed out. Are you running node proxy? If you are running on the device, check if you have the right IP address in `RCTWebSocketExecutor.m`.
2016-08-01 17:00:35.830 [info][tid:com.facebook.react.RCTBridgeQueue][RCTPerformanceLogger.m:41] Unbalanced calls start/end for tag 14
2016-08-01 17:00:39.144 WorkerSampleApp[3333:63042] No parent bridge defined - abord sending worker message
2016-08-01 17:00:44.161 WorkerSampleApp[3333:63041] No parent bridge defined - abord sending worker message
2016-08-01 17:00:49.176 WorkerSampleApp[3333:63041] No parent bridge defined - abord sending worker message
The last message repeats every 5 seconds which makes me think the worker has loaded, but the messages just aren't getting through.
Any ideas?
thanks for reporting this. can you try with master version to see if the latest changes would fix this ?
The master version is version 0.3.0? If so, then I am using the latest version.
please use v0.3.1.
note that console messages orignating from the workers cannot be displayed on the chrome console.
note that console messages originating from the workers cannot be displayed on the chrome console.
@devfd This may be readme worthy!
Also, I'm experiencing crashing when I enable chrome debugging. It looks like it's because both the app and the worker are trying to connect to the same debugger:
XCode console:
2016-08-03 10:13:28.955 FutureApp[4058:172478] starting Worker http://localhost:8081/worker.bundle?platform=ios&dev=true&minify=false
2016-08-03 10:13:29.944 [info][tid:NSOperationQueue 0x7fbe62b168f0 :: NSOperation 0x7fbe62cc5c90 (QOS: LEGACY)][RCTPerformanceLogger.m:41] Unbalanced calls start/end for tag 0
2016-08-03 10:13:30.957 [fatal][tid:com.facebook.react.WebSocketExecutor] Runtime is not ready for debugging. Make sure Packager server is running.
Packager output:
[10:13:27 AM] <END> request:/index.ios.bundle?platform=ios&dev=true&minify=false (858ms)
[10:13:27 AM] <START> request:/index.ios.bundle?platform=ios&dev=true&minify=false
[10:13:27 AM] <END> request:/index.ios.bundle?platform=ios&dev=true&minify=false (7ms)
[10:13:28 AM] <START> request:/worker.bundle?platform=ios&dev=true&minify=false
[10:13:28 AM] <START> find dependencies
transformed 624/624 (100%)
[10:13:29 AM] <END> find dependencies (690ms)
[10:13:29 AM] <START> request:/worker.bundle?platform=ios&dev=true&minify=false
[10:13:29 AM] <END> request:/worker.bundle?platform=ios&dev=true&minify=false (826ms)
[10:13:29 AM] <END> request:/worker.bundle?platform=ios&dev=true&minify=false (142ms)
[10:13:29 AM] <START> request:/worker.bundle?platform=ios&dev=true&minify=false
[10:13:29 AM] <END> request:/worker.bundle?platform=ios&dev=true&minify=false (14ms)
[10:13:30 AM] <START> symbolicate
[10:13:30 AM] <START> find dependencies
transformed 624/624 (100%)
[10:13:31 AM] <END> find dependencies (604ms)
[10:13:31 AM] <END> symbolicate (971ms)
@seantempesta any luck with this issue?
@seantempesta Any luck man?
Nope. I still don't understand what's going on either.
Sean
On Fri, Sep 30, 2016 at 2:22 AM -0700, "vicmpen" notifications@github.com wrote:
@seantempesta Any luck man?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
OK then do this: in the worker constructor don't use the relative path to the worker.js file. Instead provide a path starting from the root of you project.