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

Devtools wont work on debugger, works on local server #29

Open
LaloHao opened this issue Dec 8, 2017 · 2 comments
Open

Devtools wont work on debugger, works on local server #29

LaloHao opened this issue Dec 8, 2017 · 2 comments

Comments

@LaloHao
Copy link

LaloHao commented Dec 8, 2017

If i go into http://localhost:8081/debugger-ui/ the monitor does not do anything (no state, no actions dispatches), but if i go http://localhost:8000/ everything works fine.

There are logs in the debugger indicating something

Console was cleared
23:55:58.746 Running application with appParams: {"rootTag":91}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF
23:55:59.736 connected to remotedev-server
23:57:03.968 WebSocket connection to 'ws://localhost:8081/socketcluster/' failed: WebSocket is closed before the connection is established.
23:58:23.968 WebSocket connection to 'ws://localhost:8081/socketcluster/' failed: WebSocket is closed before the connection is established

Is there a way to debug this problem?

I also need to manually especify the default port and hostname, otherwise the server at http://localhost:8000/ won't work
remotedev-debugger --hostname localhost --port 8000 --injectserver

@LaloHao LaloHao changed the title Devtools wont work on debugger, works on Devtools wont work on debugger, works on local server Dec 8, 2017
@LaloHao
Copy link
Author

LaloHao commented Dec 8, 2017

More info:

On the terminal:

1512722765526 - Origin: Worker (PID 21025)
   [Warning] SocketProtocolError: Client pong timed out
    at SCSocket._onSCClose (/Users/hao/dev/catedral/node_modules/socketcluster-server/scsocket.js:205:17)
    at Timeout.<anonymous> (/Users/hao/dev/catedral/node_modules/socketcluster-server/scsocket.js:170:10)
    at ontimeout (timers.js:475:11)
    at tryOnTimeout (timers.js:310:5)
    at Timer.listOnTimeout (timers.js:270:5)

adb logcat:

W/unknown:ReactNative( 3797): Calling JS function after bridge has been destroyed: RCTDeviceEventEmitter.emit(["websocketMessage",{"data":"#1","type":"text","id":1}])

@crs2here
Copy link

@LaloHao were you able to ever to debug on a physical device? I am running into the same problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants