-
Notifications
You must be signed in to change notification settings - Fork 24k
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
remote debugging when running server on different port #12527
Comments
@ConnorMWGraham - did you rebuild the client using |
No. I thought I had adjusted the client appropriately by doing ctrl+M > Dev Settngs > Debug server host & port for device >"10.0.2.2:9090". Where can I find the appropriate client configuration file? |
Same issue here. I have to run packager on different port since 8081 is already taken by McAfee processes ( cannot change that easily :( ). Everything works fine when I change host & port device via "in-app menu" (CMD+M). However it returns same error as in issue description when I turn on the remote debugger. |
I believe that #12095 which has a PR that has not yet been merged will partially fix the issue. I am able to work around this currently by setting a breakpoint in debuggerWorker.js and changing the port on the message.url before continuing (see screenshot). This is a painful work around, but until that PR is merged, not sure there is a better option. However, I also needed to update the RealmReactModule.java file to change the hard coded port set for the Access-Control-Allow-Origin header to be the custom port I'm using (8088). Otherwise I get CORS errors.
After doing these two things, I was able to get the remote debugging to work. |
See #9935. |
Solved in #12095 |
Description
I am running my server with "react-native start --port 9090". I can not use port 8081. Enabling Remote JS Debugging from my android emulator produces the following error:
The error seems to be easy to understand. It is trying to load a resource from localhost:8081, but can't find it because my server is running on port 9090
Reproduction
Additional Information
The text was updated successfully, but these errors were encountered: