React Native Build Commands Failed: PhaseScriptExecution ... (domain=NSPOSIXErrorDomain, code=2)

Question

Environment

Mac OS X Version 10.11.3 (15D21)
Xcode Version 7.2 (7C68)
Simulator Version 9.2 (SimulatorApp-643)
react-native-cli 0.1.10
node v5.5.0

What I did before running the app

npm install -g react-native-cli
react-native init DemoProjectDELETEME
cd ./DemoProjectDELETEME
react-native run-ios

I am new to React Native. When I try to run the default app on iOS simulator I got the following errors. I found a similar issue but it does not solve my problem.

Xcode6 can't run any app in simulator ( Domain = NSPOSIXErrorDomain, Code = 3 )

After restart the machine and simulator the issues still persistent.

** BUILD FAILED **


The following build commands failed:
    PhaseScriptExecution Run\ Script /Users/x/Desktop/DemoProjectDELETEME/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Script-006B79A01A781F38006873D1.sh
(1 failure)
Installing build/Build/Products/Debug-iphonesimulator/DemoProjectDELETEME.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist
/Users/x/Desktop/DemoProjectDELETEME/node_modules/promise/lib/done.js:10
      throw err;
      ^

Error: Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/DemoProjectDELETEME.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

    at checkExecSyncError (child_process.js:464:13)
    at Object.execFileSync (child_process.js:484:13)
    at _runIOS (runIOS.js:77:34)
    at runIOS.js:24:5
    at tryCallTwo (/Users/x/Desktop/DemoProjectDELETEME/node_modules/promise/lib/core.js:45:5)
    at doResolve (/Users/x/Desktop/DemoProjectDELETEME/node_modules/promise/lib/core.js:200:13)
    at new Promise (/Users/x/Desktop/DemoProjectDELETEME/node_modules/promise/lib/core.js:66:3)
    at Array.runIOS (runIOS.js:23:10)
    at Object.run (/Users/x/Desktop/DemoProjectDELETEME/node_modules/react-native/local-cli/cli.js:86:13)
    at Object.<anonymous> (/usr/local/lib/node_modules/react-native-cli/index.js:73:7)

Got the follower error when I am trying to launch the app from Xcode.

sudo npm start in project root solves the issue, but react-native run-ios still BUILD FAILED.

Thanks for your time viewing my question.

it's always extremely disappointing to come across such issues when following instructions to create the basic sample project. It doesn't inspire much hope in React Native. — Max MacLeod, Jun 23 '16 at 15:23

score 18 · Answer 1 · answered Jul 18 '16 at 19:45

18

For me port 8081 was in use :

lsof -n -i4TCP:8081

answered Jul 18 '16 at 19:45

phani

1,134
1
11
24

3

Not sure why this had been downvoted, this is what fixed it for me (after reading a similar suggestion in another question). – Mike Hedman Sep 28 '16 at 04:54
Holy moly, a solution so far off from any direction debug messages pointed at. Thank you! – klaus Nov 28 '16 at 22:58
Worked for me! Yup surprised the debug message does not indicate the port is in use whatsoever – yahms23 Dec 07 '20 at 10:46
1

use `kill $(lsof -t -i:8081)` to kill the process at port 8081 – yunas Feb 26 '22 at 17:36

score 17 · Accepted Answer · answered Jul 15 '16 at 09:05

17

Try running react-native upgrade

See Github thread: https://github.com/facebook/react-native/issues/7308#issuecomment-219597774

answered Jul 15 '16 at 09:05

Nima Izadi

996
6
18

score 8 · Answer 3 · answered Jan 25 '17 at 14:14

8

1.Go to File -> Project settings 2.Click the Advanced button 3.Select "Custom" and select "Relative to Workspace" in the pull down 4.Change "Build/Products" to "build/Build/Products" 5.click done, done

answered Jan 25 '17 at 14:14

Katta Nagarjuna

1,539
2
12
12

1

thanks this helped. Could this have been duplicated by simply removing something instead? Also, the picture and text steps don't align. The ss also changed the Intermediates field. – Drew Mar 22 '17 at 12:14

score 5 · Answer 4 · answered Sep 29 '16 at 21:02

5

The problem is in the js file that builds and runs your app. Unless your project, scheme, and Product Name are all the same, you'll get errors, especially on simulators.

The good news is that I submitted a pull request that fixes the problem. Please go upvote it so we don't have worry about things breaking when we rename things.

answered Sep 29 '16 at 21:02

Steve Potter

1,899
2
22
25

1

This is the only sensible answer in this thread. You may want to also add that this behavior may persist until watchman and/or the simulator are restarted. Other than that, I cannot believe the answers given to fix this issue. I may want to add my own like "Grab your crotch, turn your head, cough three times, and then spin around", because it will help just as much as a lot of these others based on pure coincidence. – DBrown Mar 18 '17 at 17:17

score 4 · Answer 5 · answered Sep 15 '16 at 18:16

4

For me I just needed to edit the iOS project build settings

Product Bundle Identifier was not set

You need to set it for both the Project and 2 Targets

answered Sep 15 '16 at 18:16

damien murphy.

371
2
16

score 3 · Answer 6 · answered Apr 29 '16 at 16:03

3

Open your react-native project in Xcode
Create a new schema with project name.
the problem will be solved

answered Apr 29 '16 at 16:03

Aathi

2,599
2
19
16

1

didn't work. I can run the project in Xcode regardless but not on command line with react-native run-ios – Max MacLeod Jun 23 '16 at 15:21
Didn't work. A scheme with my project name already exists and is selected. – Jonathan Tuzman Jun 10 '19 at 17:50

score 1 · Answer 7 · answered Feb 06 '16 at 17:57

1

Adding sudo in front of all commands solves the problem.

sudo react-native init ProjectName

sudo chmod 777 ProjectName

cd ProjectName
sudo react-native run-ios

answered Feb 06 '16 at 17:57

XY L

25,431
14
84
143

1

Error is gone but now it says "No devices are booted" – leo7r Sep 05 '16 at 02:29
2

This will definitely cause the need for sudo every time you want to run the project in the future. Sudo should not be needed. @Aathi answer worked for me. – Tieme Sep 06 '16 at 09:51
1

Horrible answer. You can use chmod 755 (user: full, group/world: read/write) or 744 (full, read). Using 777 is an open invitation to anything and everything. If you need to ever use sudo for your projects, you may want investigate the reason why these tools and libraries are not accessible to you as a regular user. If your tools are not installed in a user-accessible folder, issues will continue to arise; you should not ever have to use 'sudo' for your projects. Instead fix your permissions: https://docs.npmjs.com/getting-started/fixing-npm-permissions – DBrown Mar 18 '17 at 17:27

score 1 · Answer 8 · answered Mar 11 '17 at 13:32

1

For me, I needed to upgrade my version of XCode from Yosemite to Sierra.

This can be done via App Store > Updates.

answered Mar 11 '17 at 13:32

Matt D. Webb

3,216
4
29
51

score 1 · Answer 9 · answered Nov 27 '20 at 01:49

1

What worked for me was running pod install from the ios directory

answered Nov 27 '20 at 01:49

green1919

289
2
13

score 1 · Answer 10 · edited Dec 27 '21 at 22:53

1

Running

npx pod-install

solved the problem for me.

edited Dec 27 '21 at 22:53

answered Dec 27 '21 at 09:59

shani diwaker

11
1

score 1 · Answer 11 · answered Oct 17 '22 at 12:29

1

For my case: If your project folder name called like "Example Project"

You must change it to "Example_Project"

Spaces are causen this error.

answered Oct 17 '22 at 12:29

omkocer

153
1
9

score 0 · Answer 12 · edited Dec 16 '16 at 15:39

Open Your Xcode project

Run it

You should have 2 errors from RCTSRWebSocket.m

add (void) to the beginning of both line :

SecRandomCopyBytes(kSecRandomDefault, sizeof(uint32_t), (uint8_t *)mask_key);

become

(void)SecRandomCopyBytes(kSecRandomDefault, sizeof(uint32_t), (uint8_t *)mask_key);

Save and Re-run your project with Xcode or terminal. It should work for sure. I have tested all the solution before, this one is the only who worked for me.

score 0 · Answer 13 · answered Dec 30 '16 at 13:56

Surprisingly, this was the solution for me: Open the file Views/RTCScrollView.m in Xcode and change the variable _refreshControl to refreshControl. All occurrences of _refreshControl were already marked as errors. The new code becomes:

- (void)setRefreshControl:(RCTRefreshControl *)refreshControl
{
  if (refreshControl) {
    [refreshControl removeFromSuperview];
  }
  refreshControl = refreshControl;
  [self addSubview:refreshControl];
}

score 0 · Answer 14 · edited Jun 06 '17 at 16:04

I fixed my issue, you can try it if you are in the same condition.

I encountered the same error:

Print: Entry, ":CFBundleIdentifier", Does Not Exist

When I clone an existing react-native project from learning react native.

I initialize (using {react-native init yourProjectName}) a new project with the same name in a different directory
copy every useful *.ios.js file to this new project from the one I clone elsewhere.

This works for me.

score 0 · Answer 15 · answered Oct 12 '17 at 13:08

Edit the file ,ProjectName/node_modules/react-native/local-cli/runIOS/runIOS.js Line no 18 : replace the entire line of code with the following :

return `build/Build/Products/${configuration}-${isDevice ? 'iphoneos' : 'iphonesimulator'}/${appName}.app`;

Line no: 146: uncomment '-derivedDataPath', 'build',

after that run the command from the terminal: sudo react-native run-ios

Henrique Jensen · Answer 16 · 2019-02-14T12:47:36.057

0

For me, my problem was that Mcafee is running on port 8081, so I run the app on a different port following this answer https://stackoverflow.com/a/50649969/5323419 Basically:

react-native run-ios --port 1234 react-native start --port 1234

I am using React native 0.55+

edited Feb 14 '19 at 12:47

answered Feb 11 '19 at 16:52

Henrique Jensen

399
3
6

score 0 · Answer 17 · answered Mar 08 '22 at 00:19

0

Try to run npx pod-install Also check the permissions. Maybe you should run react-native run-ios with sudo?

answered Mar 08 '22 at 00:19

laneboyandrew

290
6
17

React Native Build Commands Failed: PhaseScriptExecution ... (domain=NSPOSIXErrorDomain, code=2)

17 Answers17

Linked