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

0.50.1 react-native bundle android the process is undefined #16713

Closed
xiaoDC opened this issue Nov 7, 2017 · 3 comments
Closed

0.50.1 react-native bundle android the process is undefined #16713

xiaoDC opened this issue Nov 7, 2017 · 3 comments
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@xiaoDC
Copy link

xiaoDC commented Nov 7, 2017

Is this a bug report?

yes

Have you read the Contributing Guidelines?

yes

Environment

Environment:
OS: macOS Sierra 10.12.6
Node: 8.9.0
Yarn: 1.3.2
npm: 5.5.1
Watchman: 4.9.0
Xcode: Xcode 9.0 Build version 9A235
Android Studio: 3.0 AI-171.4408382

Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.50.1 => 0.50.1

Steps to Reproduce

(Write your steps here:)

  1. I run the command react-native run-android , the app did work;
  2. But when i want build bundle file with the command react-native bundle --verbose --dev true --entry-file index.js --bundle-output output.bundle, the app did work, and i find the Android Studio log the error process is undefined;
  3. I find the develop bundle file, there is
;require(50);
;require(0);

, however the output.bundle, there is only

;require(0);

the 50 package is the file react-native/Libraries/Core/InitializeCore.js,
and the code

// Set up process
global.process = global.process || {};
global.process.env = global.process.env || {};

in it.

Expected Behavior

the app using 0.50.1 can work with bundle file.

Actual Behavior

the app can not work.

@Fefbug
Copy link

Fefbug commented Nov 7, 2017

Probably link to this issue :
#16689

and the workaround :
#16689 (comment)

@xiaoDC
Copy link
Author

xiaoDC commented Nov 8, 2017

@Fefbug thanks

@stale
Copy link

stale bot commented Jan 7, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Jan 7, 2018
@stale stale bot closed this as completed Jan 14, 2018
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

2 participants