Can't create bundle: react-native-xcode.sh fails to call react-native

[heliumsoule]

I recently updated node to 5.0.0 and react-native won't compile in Xcode. Previous projects still work though. Does anyone have any thoughts? Thank you!

• react-native bundle --entry-file index.ios.js --platform ios --dev true --bundle-output /Users/[username]/Library/Developer/Xcode/DerivedData/firstP-diwselkaoasmusemncrzcyzygens/Build/Products/Debug-iphonesimulator/firstP.app/main.jsbundle --assets-dest /Users/[username]/Library/Developer/Xcode/DerivedData/firstP-diwselkaoasmusemncrzcyzygens/Build/Products/Debug-iphonesimulator/firstP.app
  ../node_modules/react-native/packager/react-native-xcode.sh: line 36: react-native: command not found
  Command /bin/sh failed with exit code 127

[greyexpert]

I have the same problem.
I found that XCode $PATH differs from terminal $PATH and it doesn't include path of nvm nodes (~/.nvm/versions/...).
I have temporary fixed it by adding source ~/.bash_profile to the beginig of react-native-xcode.sh but there should be a better solution.

[Jerrylingit]

as greyexpert's way，it works，but i still don't konw why……

[JonathanWi]

Same here, thanks @greyexpert, now to find a real solution :)

[jstowell29]

Experiencing the same issue... used @greyexpert workaround and was able to compile. Thanks

[sheets]

@greyexpert work around worked for me as well.

[bartonhammond]

I had to add '/usr/local/bin' explicitly to ~/.bash_profile along w/ @greyexpert workaround

[timfpark]

+1

[bartonhammond]

I created new project (react-native @0.14.0 and changing index.ios.js does not update in iOS simulator w/ Cmd+R. Anyone else experience this w/ this newest release?

[samsalisbury]

@bartonhammond I had to kill the initial packager that was started after react native init ... and start it again with npm start to get it to work in general.. However it's now failing in the way reported by the OP

[samsalisbury]

For me, the Xcode build script failure as originally reported started after I upgraded a 0.13.2 project to 0.14.0. I then created a new 0.14.0 project from scratch, and it all worked. I took my original index.os.js, styles.os.js, and dependencies from package.json (including 2 libraries with native components) into the fresh new project, and then this issue started again. I have not yet tried @greyexpert's trick.

Here is the relevant bit of the build log from Xcode:

DEST=/Users/xxx/Library/Developer/Xcode/DerivedData/AwesomeProject-gttzgacpenhrxsfurdqdxmuyymsa/Build/Products/Debug-iphonesimulator/AwesomeProject.app
+ react-native bundle --entry-file index.ios.js --platform ios --dev true --bundle-output /Users/xxx/Library/Developer/Xcode/DerivedData/AwesomeProject-gttzgacpenhrxsfurdqdxmuyymsa/Build/Products/Debug-iphonesimulator/AwesomeProject.app/main.jsbundle --assets-dest /Users/xxx/Library/Developer/Xcode/DerivedData/AwesomeProject-gttzgacpenhrxsfurdqdxmuyymsa/Build/Products/Debug-iphonesimulator/AwesomeProject.app
/Users/xxx/AwesomeProject/node_modules/react-native/node_modules/promise/lib/done.js:10
      throw err;
      ^

TypeError: Cannot assign to read only property 'undefined' of [object Object]
    at /Users/xxx/AwesomeProject/node_modules/react-native/private-cli/src/bundle/buildBundle.js:22:5
    at tryCallTwo (/Users/xxx/AwesomeProject/node_modules/react-native/node_modules/promise/lib/core.js:45:5)
    at doResolve (/Users/xxx/AwesomeProject/node_modules/react-native/node_modules/promise/lib/core.js:171:13)
    at new Promise (/Users/xxx/AwesomeProject/node_modules/react-native/node_modules/promise/lib/core.js:65:3)
    at buildBundle (/Users/xxx/AwesomeProject/node_modules/react-native/private-cli/src/bundle/buildBundle.js:18:10)
    at Array.bundle (/Users/xxx/AwesomeProject/node_modules/react-native/private-cli/src/bundle/bundle.js:19:10)
    at Object.run (/Users/xxx/AwesomeProject/node_modules/react-native/local-cli/cli.js:68:13)
    at Object.<anonymous> (/usr/local/lib/node_modules/react-native-cli/index.js:27:7)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
Command /bin/sh failed with exit code 1

UPDATE I don't know if it's relevant, but I'm using lots of bleeding edge ES7 features. If that might be relevant to someone who understands the problem let me know and I'll post my .babelrc etc.

[bartonhammond]

argh - @samsalisbury that was it. thanks

[samsalisbury]

np @bartonhammond

UPDATE: I have isolated the problem in my case to my .babelrc. Simply adding this file to a brand new (verified working) RN 0.14.0 project causes the above failure. I suspect this may related to some global dependencies I've installed and forgotten about which pick up on this, I'm going to try & isolate it.

Here's my .babelrc for completeness:

{
  "whitelist": [
    "es6.modules",
    "es6.arrowFunctions",
    "es6.blockScoping",
    "es6.classes",
    "es6.destructuring",
    "es6.parameters",
    "es6.properties.computed",
    "es6.properties.shorthand",
    "es6.spread",
    "es6.templateLiterals",
    "es7.trailingFunctionCommas",
    "es7.objectRestSpread",
    "flow",
    "react",
    "es7.classProperties",
    "es7.asyncFunctions",
    "es7.decorators",
    "regenerator",
    "utility.inlineEnvironmentVariables"
  ]
}

[samsalisbury]

UPDATE: I've found a few things out:

• Even a .babelrc file containing only {} was causing the above failure.
• I had a globally-installed babel-eslint 4.1.3 (RN has a dev dependency on 4.1.1). I removed this.
• Now, the {} .babelrc file now did not cause a build failure, but the above posted one still did. Progress.
• I bisected the .babelrc from above and isolated the issue to a single line whitelist entry:

{
  "whitelist": [
    "utility.inlineEnvironmentVariables"
  ]
}

The above .babelrc file plus a brand new react-native init ... project comprises a complete repro of the issue as far as I can tell. Anyone else here want to see if they get the same results?

I'm gonna see if I can live without that for now, and with RN's 4.1.1 version of babel-eslint...

NOTE: Though all of the above the packager never once showed issues.

[samsalisbury]

UPDATE: Removing the "utility.inlineEnvironmentVariables" whitelist entry from .babelrc from my original upgraded project resolved the original issue. Everything is fixed for me, I hope some of this is helpful for anyone else with these issues.