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

React packager hangs on transforming (100% 393/394) on demo app (Android). #5259

Closed
patscan opened this issue Jan 11, 2016 · 12 comments
Closed
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@patscan
Copy link

patscan commented Jan 11, 2016

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:

var {
  AppRegistry,
  Image,
  StyleSheet,
  Text,
  View,
} = React;

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:

React packager ready.

[1:31:52 PM] <END>   Crawling File System (1102ms)
[1:31:52 PM] <START> Building in-memory fs for JavaScript
[1:31:54 PM] <END>   Building in-memory fs for JavaScript (2263ms)
[1:31:54 PM] <START> Building in-memory fs for Assets
[1:31:56 PM] <END>   Building in-memory fs for Assets (2149ms)
[1:31:56 PM] <START> Building Haste Map
[1:31:58 PM] <START> Building (deprecated) Asset Map
[1:31:59 PM] <END>   Building (deprecated) Asset Map (742ms)
[1:31:59 PM] <END>   Building Haste Map (2676ms)
[1:31:59 PM] <END>   Building Dependency Graph (8194ms)
[1:32:09 PM] <START> request:/index.android.bundle?platform=android&dev=true
[1:32:09 PM] <START> find dependencies
[1:32:09 PM] <END>   find dependencies (182ms)
[1:32:09 PM] <START> transform
transforming [========================================] 100% 393/394[1:32:44 PM] <START> request:/index.android.bundle?platform=android&dev=true

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.

@facebook-github-bot
Copy link
Contributor

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.

  • If you don't know how to do something or something is not working as you expect but not sure it's a bug, please ask on StackOverflow with the tag react-native or for more real time interactions, ask on Discord in the #react-native channel.
  • If this is a feature request or a bug that you would like to be fixed, please report it on Product Pains. It has a ranking feature that lets us focus on the most important issues the community is experiencing.
  • We welcome clear issues and PRs that are ready for in-depth discussion. Please provide screenshots where appropriate and always mention the version of React Native you're using. Thank you for your contributions!

@christopherdro
Copy link
Contributor

@patscan Maybe its related to #5040?

@patscan
Copy link
Author

patscan commented Jan 12, 2016

@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.

@christopherdro
Copy link
Contributor

I'm not sure tbh. It's just a similar one I saw earlier.

If your using redux, see #4674.

@patscan
Copy link
Author

patscan commented Jan 12, 2016

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.

@gradddev
Copy link

I also have this problem with 18.0-rc.
screenshot from 2016-01-13 15-27-14

@techmentormaria
Copy link

+1 18.0-rc.

@skevy
Copy link
Contributor

skevy commented Jan 13, 2016

@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?

@patscan
Copy link
Author

patscan commented Jan 13, 2016

@skevy, here's the output:

{
  message: "TransformError: /Users/patscanlan/repos/AwesomeProject/index.android.js: Cannot read property 'error' of null",
  type: "TransformError",
  errors: [{ }]
}

@int64ago
Copy link

+1, I have the same problem

@int64ago
Copy link

@patscan Hi, I find it's the same issue as #5191 , it's the new bug of 0.18.0-rc

@skevy
Copy link
Contributor

skevy commented Jan 14, 2016

Closing this in favor of #5191 - please track there.

@skevy skevy closed this as completed Jan 14, 2016
@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

8 participants