-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Can't connect to developer's tools from real device (IOS) #712
Comments
Android works only after "adb -s reverse tcp:8081 tcp:8081" Is there any workaraunds or something i could do to connect real device to debugger? |
Running this command is necessary even with Metro and it's more of a Android thing than Haul/Metro/React Native.
|
@zamotany yes. Metro works out of the box for both platforms. Everything fine with metro (clear react-native start) and ios. |
And the error you've posted is displayed in the terminal when |
Ah, I know why it's happening, as usual iOS is behaving differently and for some reason makes a HTTP requests to |
There's not easy workaround for that. It needs changes in the haul's server itself, changing how the WebSocket server is created. |
this error haul dev server shows me in the browser when i tried to get ..../debugger-proxy. |
Well, at least we know the problem. If this reproducible, maybe it could be fixed in some of next releases) |
Hey, I'm having this issue too and I think it's kind of important. What's the point of creating such a tool if you can't use the debugger on a real iOS device? |
Environment
RN 61.5
Haul 0.17.0
Looks like by default device trying to connect to localhost:8081/debugger-proxy,
but the haul's server respond is like:
{"statusCode":404,"error":"Not Found","message":"File /debugger-proxy not found"}
Also real device connects fine if i use metro bundler instead.
i even thought i could bundle js by haul, and give the output to metro, but i dont manage to configure metro for that :D
Can you suggest something to connect real device to JS debugger/console?
Thanks!
The text was updated successfully, but these errors were encountered: