-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
React native breaks emulator networking #13340
Comments
Sorry. Forgot to include this in the original issue. My guess that it's related to react native breaking networking is because exclusively when running a my react-native project (only on the branch that has react-native, master doesn't have this problem, and no other Android projects cause this) the following message is logged to the emulator console (output of
|
I agree with @aem. I am running |
The error is showing up for me as well, but I've tested a few things and it doesn't seem to be impacting the app. Update, as far as I've tested, older Android tooling has no issues. Versions:
Test with old Android SDK versionsI installed an older version of the Android SDK using this old Homebrew formula. Emulator version:
Targets:
AVD I created:
Starting the emulator, running the app using Test with new Android SDK versionsInstall new tooling with brew cask
Install a system image:
Install tools:
Create AVD:
Starting the emulator, running the app using |
same issue |
Same issue |
See this issue on the Android issue tracker |
can't test it, getting CANNOT TRANSLATE guest DNS ip facebook/react-native#13340
Thank you for this detailed issue. Even browsing in Chrome trigger this error, however requests all seem to work correctly. On a full React Native application, if the packager can't be reached a red screen will be displayed saying that it can't reach X ip address. While React Native integration into an existing application seem to just not work. I'd say to verify every IP address in your application and be sure every connections can be reached. I had the same issue Just let me know if it was your case, so we can triage this issue. |
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally! If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution. |
Description
Quite frankly, I'm not entirely sure. As background, I'm trying to integrate react-native into an existing app. I've followed all of the instructions and for a while successfully had React code running alongside native Android code. A couple of days ago I got a new laptop from work and when I tried to run this code on the new laptop nothing was working.
I went back and made sure I had
watchman
and all other external deps installed, double-checked all of my code and it all appears to be ok, but for some reason my component never mounts. Constructor never gets called, log statements incomponentDidMount
are not executed, nothing. I know the JavaScript is loaded properly because log statements inindex.android.js
execute properly, so I'm fairly confident that there's no issue with my JavaScript. However, when I try to mount a component that is registered withAppRegistry
it doesn't work properly.I've opened a Stack Overflow question here to no avail.
Reproduction Steps and Sample Code
The relevant code to mount my component and the component itself are described in the SO question linked above.
Solution
Hopefully someone with more experience with RN internals might have seen this before? I'm genuinely at a loss. I've done everything from wiping out
node_modules
to wiping the Android SDK and removing all emulator instances from my laptop and starting from scratch. Nothing has remedied the issue.Additional Information
The text was updated successfully, but these errors were encountered: