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

rn-debugger is broken with react-native ^0.59 #35

Open
laurentS opened this issue Jul 12, 2019 · 5 comments
Open

rn-debugger is broken with react-native ^0.59 #35

laurentS opened this issue Jul 12, 2019 · 5 comments

Comments

@laurentS
Copy link

laurentS commented Jul 12, 2019

With the extraction of the cli to @react-native-community/cli, the debugger is not starting anymore, failing with FAIL Inject RemoteDev server into React Native local server, the file not found.

It seems to be looking for the server.js file in the wrong place.

I'm using version 0.8.4 with react-native 0.59.10.

@wesleycoder
Copy link

There has been months since this issue was posted and no response or work has begun.
Does anyone has a workaround meantime?

@laurentS
Copy link
Author

I tried to have a go at fixing this, but I'm changing things rather blindly and I don't really have time to dig further right now. Things I've seen:

  • rn-debugger depends on an outdated version of remotedev-server, it needs to be upgraded to 0.3.1 or whatever is current
  • there are fixes needed in both packages named above to account for the extraction of cli

It looks like a number of people have tried fixing various bits, without getting it to work fully:

@Acetyld
Copy link

Acetyld commented Jan 22, 2020

I tried so much! But i keep getting all kinds of errors. Most about the injecting part, i got it working with a old version of react. But can't seem to get it working with the new versions.. Damn i already put a good 6 hours in this

@angelod1as
Copy link

Is this repo still maintained?

@laurentS
Copy link
Author

It's not really answering the question, but might help if you're stuck: this commit shows how I got around the issue for our app. I use a different debugging tool (which I think is a bit clunkier) but it sort of works.

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

4 participants