-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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 packager hangs on transforming (100% 393/394) on demo app (Android). #5259
Comments
Hey patscan, thanks for reporting this issue! React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
|
@christopherdro Thanks for the reply. I am on 18.0-rc though, so I would think it should be resolved were it the same issue. Is there more logging I provide? I am not seeing the error from the second screenshot of the #5040 that explicitly points to babel, but perhaps I'm not knowing where to look. |
I'm not sure tbh. It's just a similar one I saw earlier. If your using redux, see #4674. |
Thanks, I had come across both of these threads before posting, but I'm afraid neither seems to quite address this. I may post on stack overflow and see if others are seeing this behavior. |
+1 18.0-rc. |
@patscan if you go to http://localhost:8081/index.android.bundle?platform=android&dev=true in your browser...does it spit out JS? Or an error? |
@skevy, here's the output:
|
+1, I have the same problem |
Closing this in favor of #5191 - please track there. |
Trying to run Android tutorial with Genymotion emulator.
OS X Yosemite
Genymotion
react-native run-android
succeeds. Following along tutorial, successfully launches app in emulator until I get to this step:App launches with red screen of death ("Unable to download JS bundle. Did you forget to start the development device..."). Noticing the following in react packager logs:
Note - hung on 393/394.
Sorry if I'm adding to noise and this issue is covered elsewhere. Seeing similar tickets that have been closed, but the
adb reverse tcp:8081 tcp:8081
command isn't working for me (I believe that would only apply to actual hardware deploys anyway?)Thanks in advance.
The text was updated successfully, but these errors were encountered: