React-native: [Master Task] Print: Entry, ":CFBundleIdentifier", Does Not Exist

[srijak]

Please see #21303 to understand why you're running into this

(_Edited by @hramos - the original issue text has been replaced with a description of the problem_)

Description

This issue describes a class of failures where the iOS build fails with the following output:

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

This error message is a red herring as the problem is not actually caused by a missing :CFBundleIdentifier entry. What this output means is that your iOS project could not be built successfully.

If you are encountering this issue, please try the following:

1. Upgrade to the latest React Native release.
2. Upgrade to the latest Xcode version.
3. Read through the Getting Started guide if you haven't in a while, and make sure your development environment is up to date.
4. Try building your project again.

If none of these resolve your issue, please read through this thread to learn about what has worked for others. Please refrain from adding "me too" comments unless you have material information that contributes to others' solutions.

[hramos]

I have not yet been able to reproduce this, on 0.45, macOS Sierra 10.12.4, Xcode 8.3.3. I have yarn installed, which means the CLI will use it instead of npm-cli, though I don't see any boost package in my node_modules/. I am able to launch the app on iOS, though I get a RedBox due to #14246.

[WhoJave]

@srijak I also come across this error , Im trying your solution now
it's OK now, tkx :)

[kyle-ssg]

Thanks for the fix @srijak, I was able to reproduce this too since upgrading from 44 to 0.45, even after clearing node_modules and installing via yarn or npm.

[HaseebYousaf]

+1 same here!

Update: downloaded and replaced boost_1_63_0.tar.gz in the .rncache folder. It seem to fix the problem for me.

[mhorowitz]

I just added code in the above rev to improve the logging around this failure. If you see it again, please post the output so we can try to narrow down what's going on here.

[pampang]

I thought I've figured out how to fix this problem.
It turns out that the node_modules/react-native/ios-install-third-party.sh did not run out right (Maybe because the network).

download files list:
https://github.com/google/glog/archive/v0.3.4.tar.gz 
https://github.com/google/double-conversion/archive/v1.1.5.tar.gz
https://github.com/react-native-community/boost-for-react-native/releases/download/v1.63.0-0/boost_1_63_0.tar.gz
https://github.com/facebook/folly/archive/v2016.09.26.00.tar.gz

So, I did the following steps:

1. download the files needed inside the .sh, put it in the ~/.rncache/.
2. copy the downloaded files into node_modules/react-native/third-party/, ran tar -zxf *** to each file.
3. build again, and worked for me.

[barbatus]

I had this issue too, but it disappeared once I used react-native-git-upgrade for the upgrade.

[iineva]

Temporary Solution

Download boost_1_63_0.tar.gz to ~/.rncache/, replace if exist.

[PaulAndreRada]

After trying absolutely everything in this tread and this one https://github.com/facebook/react-native/issues/7308 I still kept getting the same issue on:
react-native-cli: 2.0.1
react-native: 0.45.1

My build process would just error out and stop, giving me:

** BUILD FAILED **


The following commands produced analyzer issues:
    Analyze /Users/<MASKED>/node_modules/react-native/ReactCommon/yoga/yoga/YGNodeList.c
    Analyze /Users/<MASKED>/node_modules/react-native/ReactCommon/yoga/yoga/Yoga.c

(2 commands with analyzer issues)

The following build commands failed:
    CompileC /Users/<MASKED>/Library/Developer/Xcode/DerivedData/Build/Intermediates/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/Bits.o /Users/<MASKED>/node_modules/react-native/third-party/folly-2016.09.26.00/folly/Bits.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/<MASKED>.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

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

I then deleted the ios/ and android/ folders and did react-native eject then tried react-native-git-upgrade for the thousand time, and it worked!

[folivi]

Fixed by removing everything from ~/.rncache/

[Saradion]

The fix proposed by @folivi above worked perfectly for me.

For the record, I stumbled upon this issue today when creating a brand new project with react-native init
react-native : 0.46.1
react-native-cli : 2.0.1

Edit : It would appear that the above fix works on a project using [email protected], but not with [email protected].

[MrVisitor]

I had this issue too, but it disappeared once I removing everything from ~/.rncache/ and used command react-native-git-upgrade

[codler]

Reinstall node_modules rm -rf node_modules && yarn

[xareelee]

Have this issue been resolved?

Still encounter this issue with [email protected].

[mhorowitz]

My belief is that somehow the files in ~/.rncache/ are corrupted, and so unpacking them doesn't work right, but for some reason the error is not caught. https://github.com/facebook/react-native/blob/master/scripts/ios-install-third-party.sh will not re-download those files once they exist in ~/.rncache/. If you're running v0.47.0-rc.0 or newer, the debug info at line 22-24 may help confirm.

I believe at this time the correct fix is for the ios-install-third-party.sh script to encode the sha hashes of the files which it will download, and verify the contents of ~/.rncache/ against them before using them. If the hashes don't match, It can retry the download a few times. This should fix the problem for good.

If someone wants to work on this, that would be awesome, or else I will do it when I can. For now, the workaround is to rm -rf ~/.rncache as pointed out by several people above. (thanks!)

[hsuastegui]

I downloaded the library boost_1_63_0.tar.gz, replace it in ~/.rncache/ and extract it in /node_modules/react-native/third-party/boost_1_63_0 and it worked.

[Kosai106]

My fix was a match of some of the above mentioned solutions: rm -rf node_modules && rm -rf ~/.rncache && yarn

[jjerryhan]

This article would be helpful : Handling third party build error on react-native 0.46x

[messiBob]

i have try many ways, but no ways

[hramos]

Duplicate of #14447

[hramos]

_Repeating what I just said in #14447:_

I just merged several related issues. Let's avoid opening new issues for the same error message for now.

Workaround

If you run into this issue, it seems like the preferred workaround at this time is to do the following:

rm -rf ~/.rncache

Then run the run-ios command again, making sure it finishes:

react-native run-ios

IMPORTANT

Wait for the run-ios command to finish in its entirety. You should see several messages that follow this format: curl: Saved to filename 'glog-0.3.4.tar.gz'. Do not press CTRL+C to kill the process.

Thanks to @jjerryhan for arriving at the above list of steps (see Handling third party build error on React Native for an explanation behind why some people may end up in this state).

Next Steps

Help us debug the issue

In a555551aaf1de1aff2a58f7aa09e970bcd003f7f, @mhorowitz placed additional logging in the build script to help us debug the issue.

If you see the following message, Unpacking 'SOME_FILENAME_HERE' failed. Debug info:, when running react-native run-ios, please comment here with the output following the Debug info: phrase.

Contribute a fix

Marc commented earlier in this thread with some ideas:

I believe at this time the correct fix is for the ios-install-third-party.sh script to encode the sha hashes of the files which it will download, and verify the contents of ~/.rncache/ against them before using them. If the hashes don't match, It can retry the download a few times. This should fix the problem for good.

Keep the thread focused

To aid in the investigation, please refrain from adding "me too" comments unless you have new information to share.

[saadzaman]

cleaning the rncache folder still doesnt work i get this message irrespective of whatever is in the users rncache

* BUILD FAILED *

The following build commands failed:

CompileC /Users/Danis/Desktop/albums/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/yoga.build/Objects-normal/x86_64/Yoga.o /Users/Danis/Desktop/albums/node_modules/react-native/ReactCommon/yoga/yoga/Yoga.c normal x86_64 c com.apple.compilers.llvm.clang.1_0.compiler

(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/albums.app
No devices are booted.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

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

Im not sure if this is related to thirdparty or not ..

[CrazyWr]

hey, guys, I think we should download the boot_1_63_0 from here size: 11.7M rather than this size: 80+M,
and the file path is:
your-project-name/node_modules/react-native/scripts/ios-install-third-party.sh
like this:

after downloading, replace the boot_1_63_0 in your-project-name/node_modules/react-native/third-party/boot_1_63_0

[sumesh1993]

this commit seems to fix the issue Fixed issue with install third party script in directory with spaces

[AlanFoster]

Running into this issue, the solution for us was to remove spaces from the project directory path.

Potentially part of the fix:
We've installed yarn directly via brew and there was no .rncache, but I did run yarn cache clean too before removing spaces from our project directory path.

[summerstream]

I have also met with similar problem. it's because when init an react native app using command 'react-native init xxx' ,the cli will download some third party libs. So if downloaded failed you can see this error.

My solution is just go to see the source file called 'ios-install-third-party.sh' and download the four lib file and then copy to ~/.rncache directory.

Hope this can help you.

[klair]

Solved this issue by removing underscores from the project directory path.

[mounthorse-slns]

Same issue here. I've MacOs El Captain on VMware.

Node v. 7.8.0
npm v.4.6.1
react-native-cli 2.0.1
react-native 0.46.4
Xcode v. 8.2.1

I've two issues:

• when trying to init a new react-native project, the packages fetching hangs on getting react-native 0.46.4 package from repo. Other packages were downloaded successfully. So I've execute npm install from Windows and then copied the node_modules folder on Mac.
• when trying to run the project on iOS simulator I recieve the following error:

* BUILD FAILED *

...
In file included from /Users/michelebombardi/Desktop/ReactNativeProjects/caliup/node_modules/react-native/React/../third-party/folly-2016.09.26.00/folly/Bits.h:70:
/Users/michelebombardi/Desktop/ReactNativeProjects/caliup/node_modules/react-native/React/../third-party/folly-2016.09.26.00/folly/detail/BitIteratorDetail.h:21:10: fatal error: 'boost/iterator/iterator_adaptor.hpp' file not found
#include <boost/iterator/iterator_adaptor.hpp>

The following build commands failed:

CompileC /Users/michelebombardi/Desktop/ReactNativeProjects/caliup/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/Conv.o /Users/michelebombardi/Desktop/ReactNativeProjects/caliup/node_modules/react-native/third-party/folly-2016.09.26.00/folly/Conv.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/CaliUp.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

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

I really need to publish my app on the app store before the end of the week.
I've already try all suggested solutions but nothin works.

Could anyone help me?

[1yvT0s]

seems my xcode generate app file into "build/Products/..." not "build/Build/Products/...";
In proj_dir/node_modules/react-native/local-cli/runIOS/runIOS.js, this file:
const getBuildPath = function()... { return build/Products/...;};

[walty8]

@hramos I don't think it's appropriate to mark a bunch of other issues as duplicates of this issue. This issue basically means the project could not be compiled, and it could be a dozen of reasons (project name problem, cache problem, etc..).

But for other issues, e.g. #14404, they have very explicit reason for the error.

In my case, this is how I solved the problem:

1. the command of react-native run-ios only brought a very vague error message (as titled), however using xcode to open the .xcodeproj project in<project>/ios and explicitly build would give a much helpful message. In my case, it's boost/iterator/iterator_adaptor.hpp file not found

2. (I suspect) the automatic download of boost_1_63_0.tar.gz has some problems. And the first build of project caused a false cached extract folder in the project. So I need to replace both. (see below)

3. as mentioned by @CrazyWr, I downloaded the new boost_1_63_0.tar.gz from https://github.com/react-native-community/boost-for-react-native/releases

4. And I also removed the folder of <project>/node_modules/react-native/third-party/boost_1_63_0/boost, and copy an extracted folder from boost_1_63_0.tar.gz to there

5. use xcode to clean and rebuild the project (no need to restart xcode)

6. now react-native run-ios works too

[hramos]

We're tracking a particular failure in this master task. If you're confident your issue is unrelated to this one, please go ahead and create a new task.

[yohanceli]

@PaulAndreRada It's work for me

[panuhorsmalahti]

Solved by updating from OS X El Capitan to macOS Sierra and from XCode 7 to XCode 8.8.3.

[jomanessdev]

Still does not work for me (OSX Sierra 10.12.6; Xcode 8.3.3; react 16.0.0-alpha.12; react-native 0.48.3).

Steps to error:

1. react-native init project_name
2. cd project_name
3. react-native run-ios

Error:

PhaseScriptExecution Start Packager /Users/jomaness/Repos/mohm_app_2017/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Script-006B79A01A781F38006873D1.sh
cd /Users/jomaness/Repos/mohm_app_2017/node_modules/react-native/React
/bin/sh -c /Users/jomaness/Repos/mohm_app_2017/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Script-006B79A01A781F38006873D1.sh

Connection to localhost port 8081 [tcp/sunproxyadmin] succeeded!

Port 8081 already in use, packager is either not running or not running correctly

Command /bin/sh failed with exit code 2

* BUILD FAILED *

The following build commands failed:
PhaseScriptExecution Start Packager /Users/jomaness/Repos/mohm_app_2017/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Script-006B79A01A781F38006873D1.sh
(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/mohm_app_2017.app
No devices are booted.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

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

What I've tried:

• Replacing /node_modules/react-native/third-party/boost_1_63_0/boost w/ https://github.com/react-native-community/boost-for-react-native/releases download. Still nothing.
• Building in xcode I get error:
  > Connection to localhost port 8081 [tcp/sunproxyadmin] succeeded!
  > Port 8081 already in use, packager is either not running or not running correctly
  > Command /bin/sh failed with exit code 2

Can someone help ?

[acilgit]

n my case, this is how I solved the problem:

the command of react-native run-ios only brought a very vague error message (as titled), however using xcode to open the .xcodeproj project in/ios and explicitly build would give a much helpful message. In my case, it's boost/iterator/iterator_adaptor.hpp file not found

(I suspect) the automatic download of boost_1_63_0.tar.gz has some problems. And the first build of project caused a false cached extract folder in the project. So I need to replace both. (see below)

as mentioned by @CrazyWr, I downloaded the new boost_1_63_0.tar.gz from https://github.com/react-native-community/boost-for-react-native/releases

And I also removed the folder of /node_modules/react-native/third-party/boost_1_63_0/boost, and copy an extracted folder from boost_1_63_0.tar.gz to there

use xcode to clean and rebuild the project (no need to restart xcode)

now react-native run-ios works too

It works!! thank u

[lingliMr]

@walty8
It works!! thank u

[nguyendv]

@jomanessdev This is the your message: "Port 8081 already in use, packager is either not running or not running correctly", which probably a packager is running. Is there any chance a react-native run-ios or a react-native run-android has been running?

[nguyendv]

In my case, I can confirm the error is caused by Unpacking '/Users/nguyendv/.rncache/boost_1_63_0.tar.gz' failed, which means the downloaded boost_1_63_0.tar.gz is corrupted.

When I manually tried to download it the first time, it's quite slow and eventually stopped at 7MB/11MB. I suspect either my internet is too slow or the s3 host has some issue.

[creeperyang]

I tried all solutions pointed above, and all failed.

I download boost_1_63_0.tar.gz and replaced it at ~/.rncache as @iineva said. And then

1. I delete the whole project and re-create with the command react-native init proj.
2. cd proj && react-native-git-upgrade (npm install -g react-native-git-upgrade firstly).
3. Finally react-native run-ios succeeds.

Hope it helps.

react-native-cli: 2.0.1
react-native: 0.48.3
node: 8.4.0
xcode: 8.3.3

[wko27]

My fix to this was to open XCode (to workspace if using Pods or project if not), then click on project in Project Navigator and manually edit the "Bundle Identifier" property in the General tab. Exit XCode, then run react-native run-ios

[mhorowitz]

I've committed a fix for the problem of corrupted files in ~/.rncache. See the "Workaround" section in the original post for how to use it.

[jqn]

For me, I was able to run my project with Xcode but it would fail with react-native run-ios. I figured out it was a really easy fix. From Xcode make sure your system is using the latest version of command line tools. Preferences... then the Locations panel and check the latest version of Command Line Tools is selected.

From https://facebook.github.io/react-native/docs/getting-started.html

[dcalixto]

The Same issue here!

(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/booty.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

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

[moosebay]

This solution worked for me after removing the rncache, the workaround on this page. I hope it works for you.

https://stackoverflow.com/questions/46208317/xcode-stdint-h-error-this-file-should-only-be-included-when-compiling-with-msvc

[tjkang]

I've tried all of those above but still didn't fix the problem
but I tried this https://github.com/facebook/react-native/issues/7308#issuecomment-250231736
and it finally solved the problem!

[hellolake]

I've solved this issue via:

$ rm ~/.rncache/*
$ rm -rf xxx/project/node_modules/react-native/third-party/*
$ vi ~/.curlrc
Insert proxy = http://x.x.x.x:port

Finally "BUILD SUCCEEDED" shows, but...

Another issue comes orz:

tar: qtn_file_apply_to_path(boost_1_63_0/._boost.dAG8VY): Operation not permitted
tar: qtn_file_apply_to_path(boost_1_63_0/boost/._.DS_Store.LWaUjm): Operation not permitted
tar: qtn_file_apply_to_path(boost_1_63_0/boost/._accumulators.r6Lc7B): Operation not permitted
...

It also happens via doing download & replace those third-part files. The project looks running good, may this is just some warnings or weak errors?

---

Node 8.7.0
NPM 5.4.2
React Native 0.49.3
RNCLI 2.0.1
Yarn 1.2.1
macOS Sierra 10.12.1
Xcode 8.3.3

[spotelf13]

Solved this by:
$ rm -rf node_modules && rm -rf ~/.rncache && yarn or npm install
$ react-native upgrade

Dependencies used:

"react": "^16.0.0",
"react-native": "^0.44.3",
"react-redux": "4.4.0",
"redux": "3.3.1",
"redux-thunk": "1.0.3"

* BUILD SUCCEEDED * 👍

[sapher]

@spotelf13 Thanks it solved my issue, the react-native upgrade part did the trick

[BobAleena]

@srijak's workaround seems to have worked for me. Thank you!

[SteveAlexander]

I had the problem described in this issue. Turns out my default build location in xcode was not set to what runIOS.js expects.

To diagnose the problem, I followed the guidance on https://pewpewthespells.com/blog/xcode_build_locations.html

You can check the overall build location setting with defaults read com.apple.dt.Xcode IDEBuildLocationStyle, which might be Custom.

If it is Custom, then also check defaults read com.apple.dt.Xcode IDECustomBuildLocationType which should for me be RelativeToWorkspace, and also defaults read com.apple.dt.Xcode IDECustomBuildProductsPath which should be build/Build/Products.

If the latter is not build/Build/Products but is instead build/Products (that is, missing a Build/), then reset it like this: defaults write com.apple.dt.Xcode IDECustomBuildProductsPath "build/Build/Products".

At this point, running the iOS simulator should work.

[Ghoss91]

I tried every solution found on the page and none of them worked for me !
I'm on macbook pro yosemite 10.10.5 and I use xcode 7.0
is up to you to find which version of react native is compatible with your Xcode version that you use.
for my case I taped''' react-native init ProjectName --version 0.34.0 ''' and it worked

-

[SPxiaomin-zz]

@hellolake If in China(i'm am the same as you), set the proxy for curl and then it works.

File: ~/.curlrc
proxy = http://x.x.x.x:port

@srijak maybe this is a solution for programmer in China.

[SidharthRaveendran]

@spotelf13 thank you! this solved my issue

$ rm -rf node_modules && rm -rf ~/.rncache && yarn or npm install
$ react-native upgrade

Dependencies:

"react": "^16.0.0",
"react-native": "^0.49.3",

[Jun711]

It could be because of not up-to-date XCode too. Upgrading XCode to 9+ might help.

[noahbuscher]

Yeah I only fixed this by copying my src, package.json, and index.js files over to a separate directory, starting fresh with react-native init <name>, dragging the source files _back_ to the new directory, and building with react-native run-ios.

Using:

"react": "^16.0.0",
"react-native": "^0.49.3"

Not optimal by any means, but it's at least building to the simulator now.

[Nauzer]

What worked for me in solving this issue was

rm -rf /ios/build && react-native run-ios

from project directory
There are still some 'Analyzer issues' reported afterwards but the build succeeds.

[BuffMcBigHuge]

Nothing here have solved my issues with react-native run-ios and the CFBundleIdentifier issue. My only solution is to build from Xcode.

OS: MacOSX High Sierra 10.13.1 (17B48)
Node: 8.9.1
npm: 5.5.1
Xcode: 9.1
React Native: 0.49.5
React: 16.0.0

[kis]

@hramos @srijak

Also have the same errors, and nothing helped
mkdir: third-party: Permission denied
** BUILD FAILED **
Print: Entry, ":CFBundleIdentifier", Does Not Exist

OS: MacOSX High Sierra 10.13.1
Node: 8.9.1
npm: 5.5.1
Xcode: 9.1
React Native: 0.47.2
React: 16.0.0-alpha.12

[kis]

@hramos @here

Updated React Native to 0.50.0 and React to 16.0.0 and get the same but much more info like

folly-2016.09.26.00/folly/test/ThreadNameTest.cpp: Failed to create dir 'folly-2016.09.26.00'Can't create 'folly-2016.09.26.00/folly/test/ThreadNameTest.cpp'

Failed to create dir repeats many times

Anyone has some thoughts according to this?

[hramos]

Hey all - this error can mean many different things, hence why so many issues get opened about it. I'll leave this thread open so that people may discover suggested workarounds. I'll edit the original post to make it clear it may not refer to any particular issue. I may consider closing comments in the future if needed, but I don't want to encourage new issues to be opened.

[pkshefi]

node_modules/react-native/local-cli/cli.js start --reset-cache

worked for me (o_0) peace out

[findmory]

@SteveAlexander Your info led me to the solution but I needed to make the changes from inside Xcode Prefs.

in Pref> locations I left Derived Data: Default but after clicking "advanced" i changed my build location to "Custom" > Relative to Workspace and set Products to: "build/Build/Products"

This solved it for me!
I have XCode 9.2 (9C40b)
react-native-cli: 2.0.1
react-native: 0.51.0
MacOS 10.12.6

[ghost]

My issue was because I forgot to run pod install in the ios directory, because I use CocoaPods. I had cleaned up the Pods folder and react-native run-ios was trying to look or stuff inside it. The error logging reflected this prior to the generic CFBundleIdentifier error.

[ddereszewski]

My problem was that I was able to run the project directly from xcode but not from command line.

The problem was that in ios/ folder there where two project files
MyNewApp.xcworkspace
MyNewApp.xcodeproj

The first one was created as a installation step for some dependency library.

Simply removing the .xcworkspace directory solved the problem to me.

[ghost]

The xcworkspace is generated when you use CocoaPods.

[Ifychim]

Still getting this error and none of the solutions above have resolved my issue, anyone know the cause?

CompileC /Users/ifychim/Library/Developer/Xcode/DerivedData/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/raw_logging.o /Users/ifychim/Desktop/$/Icebreaker/node_modules/react-native/third-party/glog-0.3.4/src/raw_logging.cc normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/ifychim/Library/Developer/Xcode/DerivedData/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/signalhandler.o /Users/ifychim/Desktop/$/Icebreaker/node_modules/react-native/third-party/glog-0.3.4/src/signalhandler.cc normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(2 failures)

Installing build/Build/Products/Debug-iphonesimulator/Icebreaker.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

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

[Ifychim]

Lol really weird how I got this fixed...

1) Created a new : react-native init Project
in a directory that I usually created my react-native projects in.

2) ran the command npm install -g react-native-cli again.

3) react-native run-ios

Although the build was successful, I still get a few analyzer errors.

* BUILD SUCCEEDED *

The following commands produced analyzer issues:
Analyze /Users/ifychim/Desktop/reactNativePractice/Icebreaker/node_modules/react-native/ReactCommon/yoga/yoga/YGNodeList.c
Analyze /Users/ifychim/Desktop/reactNativePractice/Icebreaker/node_modules/react-native/ReactCommon/yoga/yoga/Yoga.c
Analyze Base/RCTModuleMethod.mm
(3 commands with analyzer issues)

[Bolza]

I tried all the solutions above, including the workarounds, nothing works.

I think it's XCode 9. It used to work fine with the previous version.

An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The bundle identifier of the application could not be determined.
Ensure that the application's Info.plist contains a value for CFBundleIdentifier.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

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

Seriously we still don't have a fix for this?

[mhorowitz]

As @hramos said: "this error can mean many different things, hence why so many issues get opened about it." I wish this wasn't the case, but we can't really control Xcode's limited diagnostic output. I've fixed a couple causes for this already. Unfortunately, posting the error message alone is not enough to understand what's going wrong. We really need a full end-to-end repro, so we can make it happen locally and dig into it.

[Bolza]

@mhorowitz thanks for the answer.
If you have time here's the public repo of the project, i'd really appreciate if you had time to give it a look.

I'm running on macOS 10.13.2, in this repo the react-native version is a bit old but updating to 0.51.0 doesn't improve the situation.

[agoransson]

I'm experiencing this also with a brand new project created with react-native init ... without any spaces in my path (I don't use spaces in paths...)

What I've tried so far:

• Tried deleting third party dir
• Tried replacing the boost lib with that provided by hramos
• Tried deleting ~/.rncache
• Tried manually calling the ios-install-third-party.sh script (which seems broken!)
• Tried downloading the four files manually without the seemingly broken hash-check
• Tried setting a different bundle id in xcode

None of these "fixes" work for me
The very same project compiles and runs on both Android and Windows - basic "init" project, no extra 3rd party libs, no code changes.

Any bright ideas are welcome.

react-native-cli: 2.0.1
react-native: 0.50.0
yarn: 1.3.2
npm: 5.6.0
node: v9.3.0 (if that matters at all...)
xcode: 9.2

Installing build/Build/Products/Debug-iphonesimulator/TestApp.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

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

[ghost]

@agoransson What is the value of <key>CFBundleIdentifier</key> inside build/Build/Products/Debug-iphonesimulator/TestApp.app/Info.plist? Does it match the one inside your Info.plist file in your project directory?

[mhorowitz]

@Bolza I took a look. The problem is exactly the problem identified here: https://github.com/facebook/react-native/issues/14326#issuecomment-334613408
Recursive includes in Xcode are not scalable, and cause problems like this which are hard to diagnose. Not all recursive includes will cause problems, but some will.

In this case, the actual bug is in RNGoogleSignin. There's a header search path entry which is recursive. (It's not the only one in the project or the tree, but it's the one which is causing the build to fail.) If you make it non-recursive, then the build (almost) succeeds. It looks like there's an open pull request https://github.com/devfd/react-native-google-signin/pull/304 to fix this.

(The build almost succeeds because react-native-svg is missing from packages.json. When I add it, the app compiles, links, and runs, then gets a js error. I did not diagnose further.)

[mhorowitz]

To anybody who reads this:

If you're having problems, look at the full build output, not just the last few lines. For the repro in my previous comment, here's the end of the output: https://gist.github.com/mhorowitz/ea67d8e1793e803b2ca273395ac12ed2. The important lines are 9-10, about 80 lines before the ones in the original report. This was the hint to me about the root cause. Another option is to open the project in Xcode and ⌘B to build it. The build errors there should also help find the actual cause.

This is also why having a full repro is so helpful. Someone trying to debug can see all the relevant errors and input files. Even with the errors in the gist above, without being able to see the full list of dependences and look at their project files, I could not have identified the actual bug.

I did not understand until now that the error in the original bug report just means that the app didn't compile or link. Given that, I'm going to close this issue. The error is too generic to give direction, and doesn't indicate whether the error is in React Native, third party libraries, or application code.

At this point any further issues must include a more specific error, and ideally include enough to reproduce. Please open new issues for those. Thanks!

[agoransson]

@RobertSheaO The folder structure doesn't exist fully, the folder TestApp.app is missing, and as a consequence all of it's contents too.

[agoransson]

While creating a new issue, as per instructions from @mhorowitz, I stumbled across one line in the output I had missed before. It appears it was having trouble with the libreadline.6.dylib. A simple symlink fixed my problem.

Error:
dyld: Library not loaded: /usr/local/opt/readline/lib/libreadline.6.dylib

I'm unsure if this is related to react-native being very particular about which versions to use of certain libs, because I have libreadline.7.0.dylib in there already. Anyway, my fix was this:

sudo ln -s /usr/local/Cellar/readline/6.3.8/lib/libreadline.6.dylib /usr/local/opt/readline/lib/libreadline.6.dylib

[vish-udp]

Looks like this is an issue with _Xcode Build Location_. Try switching it to Unique under Xcode -> Preferences -> Locations -> Advanced.

[dayze]

None of this previous solutions works for me.
I tried this and well it's running :)

Running into the same issue here after upgrading from 0.44. None of the above solutions or clearing caches did the trick for me. Here's what I did to get things working again:

In the Terminal, navigate to the react-native/third-party/glog folder inside node_modules (for me, this was cd node_modules/react-native/third-party/glog-0.3.4)
Once actively in this folder, run ../../scripts/ios-configure-glog.sh
Glog is configured and the required config.h header file is created for Xcode to find

https://github.com/facebook/react-native/issues/14382#issuecomment-313163119

[ptvandi]

@SidharthRaveendran's solution worked for me. I did a few additional steps beforehand so I'm not sure if they're needed.

$ rm -rf /ios/build && cd ios && pod install
$ cd .. && rm -rf node_modules && rm -rf ~/.rncache && npm install
$ react-native upgrade
$ react-native run-ios

Dependencies:

    "react": "^16.0.0-beta.5",
    "react-native": "^0.53.3"

Edit

It appears that running react-native upgrade created an entire directory inside of ios with my React Native build so the react-native run-ios command was just showing the RN app, not the one integrated into the previous app. I downgraded to react-native 0.51.0 and compiled in Xcode and am at least running for the time being. I'm building a POC so it's not a longterm fix.

TL;DR: The original commands appear to have not worked correctly so I downgraded to react-native 0.51.0.

[dbyilmaz]

@ptvandi it is work :)

[catherinetcai]

@ptvandi Downgrading to react-native 0.51.0 resolved my issues as well. Cheers.

[jstowers]

@ptvandi, thanks for a good solution!

Errors:
"dependencies": { "react": "^16.3.0-alpha.1", "react-native": "0.54.1" }

Downgraded Solution:
"dependencies": { "react": "16.2.0", "react-native": "0.53.3" }

[ann0nip]

I just re-installed Xcode to the latest version and It's working fine now.

[smartworld-dm]

I've met that error, I passed these steps and finally succeeded to build.

1) delete 'ios' and 'android' folder.
2) delete 'node_module'
3) npm i
4) react-native eject
5) react-native-git-upgrade  #this step is important
6) react-native run-ios

[masako-yamada]

If you got this error suddenly though it worked so far well, then simply you can try cleaning the project on XCode.
Product -> Clean (shortcut is shift + command + K)
Then
react-native run-ios

[havinhthai]

@smartworld-konoha Worked 👍

[tjwudi]

For those who tried everything - Check whether or not you are using a legacy XCode. It appears to me that the actual reason why I ran into this issue was actually the last couple lines of the error output:

CompileC /Users/John/Library/Developer/Xcode/DerivedData/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Objects-normal/x86_64/RCTFont.o Views/RCTFont.mm normal x86_64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

This indicates that I'm running into #18238. Updating XCode worked perfectly. Hope this helps. :-)

[tmaly1980]

FYI, this will happen when xcode fails to build, it's a very misleading error message. It seems that the Info.plist file won't be copied to the build folder if build fails before, even though it will still try to install/launch the app.

What I found was adding --verbose to react-native run-ios gave me better information as to what xcode was doing. Specifically look out for error messages amongst the warning messages.

It sounds like the common case with the third-party files can cause this ambiguous error message, even though it could mean many different issues too.

[dotmike]

This worked for me.

Open Workspace in XCode
If Xcode > 9 run command react-native upgrade

then

1. Go to File -> Workspace 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"

[saggiyogesh]

Upgraded RN 0.33 to 0.55, gives this issue.
My config:

Environment:
  OS: macOS Sierra 10.12
  Node: 8.11.1
  Yarn: 0.17.8
  npm: 5.6.0
  Watchman: 4.7.0
  Xcode: Xcode 8.1 Build version 8B62
  Android Studio: 2.2 AI-145.3276617

Packages: (wanted => installed)
  react: 16.2.0 => 16.2.0
  react-native: 0.53.3 => 0.53.3

So instead of using 0.55(latest), downgraded RN to 0.53.3 and everything's worked fine. I think, 0.55 version works with Xcode 9, not with Xcode 8.

Following commands are helpful:

• rm -rf ios android node_modules ; npm i ; react-native eject
• react-native run-ios

Hope this helps.

[sheminusminus]

In case others are still having this issue, there are some fixes mentioned above that were close to what I needed, but not quite. For me, the solution was:

1. In Xcode, go to File > Workspace Settings
2. In the first settings screen that launches, change the selection for Derived Data to Workspace-relative location, i.e.--

For me, the default option was pointing to an entirely different (and totally random) directory.

[abmirayo]

For me, it worked just to delete the .rncache directory in my home folder, then delete node_modules and run yarn install to install dependencies again.

[dbnex14]

None of the suggestions above are working. I am still having same error and @srijak 's suggestion how to recreate this by simply creating new project is incorrect. If I create brand new project, I can run it in both IOS and Android with no issue.
But following few suggestions how to add GoogleMaps, all result in this error so following for example this link will land you with that error
https://medium.com/quick-code/react-native-location-tracking-14ab2c9e2db8 but again every single attempt to add Google Maps resulted in this issue. Interestingly, it works fine on Android, it is only iOS that is the problem.

react-native-cli 2.0.1
react-native 0.55.4
macOS High Sierra, MacBookPro
npm 5.5.1
node -v 8.9.1
watchman 4.9.0

I tried all suggestions above and while the issue is easily reproducible, the error still exists. Also, number of other tickets were created and closed claiming this one or some other solve the issue, yet issue is still present

As explained earlier, I tried number of online articles to add Google Maps/Arbnb Maps (react-native-maps) when I started seeing this issue only in IOS. Some of these articles are below for people to try, you should get this error if you try, for example, both of these link if followed will produce this error. I also tries numerous suggestions here or elsewhere, none of which worked.
https://www.codementor.io/uokesita/integrate-airbnb-google-maps-in-a-react-native-app-dxjp5p5ed
https://medium.com/quick-code/react-native-location-tracking-14ab2c9e2db8

** BUILD FAILED **

The following build commands failed:
    CompileC build/Build/Intermediates.noindex/locationTracking.build/Debug-iphonesimulator/locationTracking.build/Objects-normal/x86_64/AppDelegate.o locationTracking/AppDelegate.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler

(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/locationTracking.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The bundle identifier of the application could not be determined.
Ensure that the application's Info.plist contains a value for CFBundleIdentifier.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

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

[auxilioivy]

cd ./ios/build
mkdir Build
cd Build

then, I symlink the folders:
ln -s ../Products .
ln -s ../Intermediates

and last react-native run-ios to work again
have a nice day :)

[dbnex14]

@auxilioivy I appreciate the confidence but that resolved noting for me. Are your steps exact and correct? I followed them exactly and all I get is another error. This is what I did exactly as you explained above

cd ios
cd build
in there I already had Build directory
rm -r Build
mkdir Build
cd Build
ln -s ../Products .
ln -s ../Intermediates

cd back to project root and issue react-native run-ios

This resulted in error below

[** BUILD FAILED **

The following build commands failed:
    Check dependencies
(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/MapExample.app
An error was encountered processing the command (domain=MIInstallerErrorDomain, code=3):
Can't stat /Users/dinob/reactnativework/MapExample/ios/build/Build/Products/Debug-iphonesimulator/MapExample.app: No such file or directory
Underlying error (domain=NSPOSIXErrorDomain, code=2):
    The operation couldn’t be completed. No such file or directory
    No such file or directory
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/MapExample.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist](url)

[urikphytech]

The error I was getting was: boost/static_assert.hpp file not found thrown from Folly.
What worked for me, after a good couple of hours, was:

1. Delete ios/Pods folder
2. Delete Podfile.lock
3. Reinstall pods using cd ios and pod install

[ham118]

Still having issue and not able run app in iOS simulator, every time message show “Print: Entry, ":CFBundleIdentifier", Does Not Exist”

Environment:
macOS High Sierra: 10.13.4
Node: 10.4.1
npm: 6.1.0
Brew: 1.6.2
Watchman: 4.9.0
Xcode: Xcode 9.4

[jsonkao]

This thread is ginormous...for the newcomers, @PaulAndreRada's solution worked for me:

I then deleted the ios/ and android/ folders and did react-native eject then tried react-native-git-upgrade for the thousand time, and it worked!

[ham118]

@jkao1 I have tried this way (@PaulAndreRada`s solution) but also it does not work.

[RicardoBarroso]

It worked for me after cleaning ".rncache":

rm -rf ~/.rncache/

and I also disabled "Find Implicit Dependencies" (and I already had "Parallelize Build disabled) on my target Build scheme settings.

[dbnex14]

rm -rf ~/.rncache/ did not resolve this issue for me at all

[ham118]

@RicardoBarroso (cleaning ".rncache") Does not resolve this issue.
After this solution has been applied, still showing
"Print: Entry, ":CFBundleIdentifier", Does Not Exist" error.

[augustbjornberg]

+1

Tried everything, still getting "Print: Entry, ":CFBundleIdentifier", Does Not Exist" error.

[heyjoy21]

I tried everything on single run

1. run lsof -n -i4TCP:8081
   COMMAND PID USER FD TYPE
   node 63635 veer 20u
   sudo kill 63635
   then
2. rm -rf ~/.rncache
   then
3. rm -rf node_modules
   then
4. yarn or npm install
   then
5. download boost_1_63_0.zip
6. goto node_modules/react-native/third-party then delete boost_1_63_0
7. now extract the downloaded boost_1_63_0.zip to node_modules/react-native/third-party folder
8. now run - react-native run-ios

Boom.. It works..

[Tomekmularczyk]

Why is this closed? I tried 4 or 5 solutions and none of them work.

[raphaelboukara]

Same for me, is there another place to track this issue?

[ham118]

Same for me, tried everything but always getting
"Print: Entry, ":CFBundleIdentifier", Does Not Exist" error.
Nothing works for this issue.

[ham118]

@heyjoy21 I have tried your solution but also It does not resolve this issue.

[apppro123]

I have the same issue.
But I don't event find the file .rncache in my project. Where do you have that file or do I have to download it myself?

Thank you for the response.

[heyjoy21]

@HazT I guess you have to create new workspace. Do the same thing again & create a new project/workspace. Make sure you have closed Xcode.

[marceloogeda]

@apppro123 the .rncache file is not inside your project. you can found it in ~/

[apppro123]

Thank you. now I have found it.

[ham118]

@heyjoy21

I have tried with the new workspace and done the same things with closed Xcode but still throw below error:

_Installing build/Build/Products/Debug-iphonesimulator/AwesomeProject.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

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

[apppro123]

I also still struggle with it:

he following build commands failed:
CompileC /Users/ProGram1/OwnAppIOS/ios/build/Build/Intermediates.noindex/RCTText.build/Debug-iphonesimulator/RCTText.build/Objects-normal/x86_64/RCTUITextView.o TextInput/Multiline/RCTUITextView.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler

(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/OwnAppIOS.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

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

[rvignesh89]

I managed to fix the problem for myself (Not sure if everyone else is facing the same situation though)

TL;DR

The fix is to ensure environment variables are present in the build log

Yeah, I know you are like 🤯. I am too. Let me explain a little more.

So based on the following error I figured that the Info.plist was not present at the location that PlistBuddy was expecting.

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/appname.app/Info.plist

When I went into the folder rightfully so, Info.plist was present in build/Build/Products/Debug-iphonesimulator/schemename.app/Info.plist. So I tried to figure out how run-ios resolves to my schema name which led me to the following code in react-native/local-cli/runIOS/runIOS.js

206:       let productNameMatch = /export FULL_PRODUCT_NAME="?(.+).app"?$/m.exec(buildOutput);
207:       if (productNameMatch && productNameMatch.length && productNameMatch.length > 1) {
208:         return resolve(productNameMatch[1]);//0 is the full match, 1 is the app name
209:       }

Basically the name is being read from an environment variable FULL_PRODUCT_NAME which is exported while the build happens. And since I turned off the env variables logging during build because I found it verbose and annoying, FULL_PRODUCT_NAME was null. But then it still resolves to my scheme name because of this line.

152:     if (!appName) {
153:       appName = scheme;
154:     }

This explains why removing ~/.rncache does not work for some people (including myself) and why recreating the project works for others because by default environment variables must be turned on.

[GreenRidingHood]

this is really weird, every time when i face that error, i am fixing with different suggestions, one time fixed with @dotmike and @sheminusminus, and this time I solved @barbatus suggestion and run react-native-git-upgrade on the terminal

[williamdarkocode]

There are several info.plist files in my ios directory. Which one needs to have a reference to the CFBundleID?

[apsuva]

xcodebuild: error: Unable to find a destination matching the provided destination specifier:
{ id:978DA498-5036-4EFA-A1D2-FF1148CB3948 }

run react-native run-ios --simulator="iPhone 7"

[omi10859]

It's not working, nothing is working
I'm losing my faith in react-native now

[phasedarray]

I found this issue may come out if 8081 port is occupied(In my case it is occupied by McAfee).
Run command sudo lsof -i :8081 to check which process has token the 8081 port.
Or you can run react-native run-ios --port 8082 to specify another port, but you need to change the port in code too.

[JeffKGabriel]

so this issue has plagued me forever
basically the error reporting just defaults to cfbundleIdentifier for many errors, when you run in terminal with react-native run-ios

What I did to fix mine is, run it in xcode and look at the error xcode outputs

• For me it was a project file (png) that i had linked to, but wasnt included in the project files and the build couldn't find it on other computers

I hope it helps a little:)

[enzoferey]

I had a problem related to glog-0.3.4 not finding a file named "config.h" and it was causing the CFBundleIdentifier error.

Solved it with this steps:

1. Close Xcode.
2. cd <Project-Folder>/node_modules/react-native/third-party/glog-0.3.4
3. Run ./configure

My project is a standard react-native init with react-native v0.55.4 (breaking changes of Babel 7 has too many errors with Jest environments right now so I don't want to update yet).

[messiBob]

在 2018年8月8日，下午10:05，Omkar [e-mail] 写道：

It's not working, nothing is working
I'm losing my faith in react-native now

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/facebook/react-native/issues/14423#issuecomment-411417129, or mute the thread https://github.com/notifications/unsubscribe-auth/AZLspyrgvAacqpqPWPbSVFTPtIYfg365ks5uOvBGgaJpZM4N1cxv.

This problem maybe cause of your react-native javaScript code incorrect , do not about the CFBoundleID , please keep the enthuasiasm of react-native

[sonnytron]

For what it's worth, I can't get this working for a completely blank project.
Xcode 9.4 or Xcode 10 beta, neither command line tools.
NPM fully updated, latest version of react-native, node, npm and everything.
I do not think it's anyones' build configuration or changes to their JavaScript code.
Because I literally cannot even get an empty new initialized project to build.

[williamdarkocode]

@sonnytron yes screw xcode. But if your're willing to try, rm-rf ios, and react-native upgrade. will reinstall all ios build files, then react-native run-ios to re build. you can even try rm-rf node_modules and npm install

[sonnytron]

@williamdarkocode thank you but that didn't fix it. Literally a vanilla project won't build.

[woohoou]

Same problem using ignite latest versions of everything...

[ghost]

If anyone still having the same problem, after running all the proposed methods to no solution, I found that brew upgrade gawk enabled some of the scripts used by react-native to run properly, and then afterward I had no problem running react-native run-ios. My ENV is:

  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
      Memory: 228.12 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 10.9.0 - /usr/local/bin/node
      Yarn: 1.9.4 - /usr/local/bin/yarn
      npm: 6.2.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        Build Tools: 23.0.1, 26.0.3, 28.0.0
        API Levels: 23, 26, 27, 28
    IDEs:
      Android Studio: 3.1 AI-173.4819257
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.4.1 => 16.4.1
      react-native: 0.56.0 => 0.56.0

[heyjoy21]

@HazT try with sudo

[Guy783]

Heres what I did

1. started by deleting the root folder that I tried to install to and creating a new one with a new name
2. ran react-native init myAppName
3. ran cd myAppName
4. ran npm install
5. ran react-native upgrade
6. ran react-native link

And it worked perfectly, first time.
Was able to run iOS from xCode

[ferdelamad]

run in your terminal: killall -9 node

That solved it for me!

[jeremyis]

I was getting Print: Entry, ":CFBundleIdentifier", Does Not Exist from a brand new React-Native project.

I tried a bunch of the things in this thread and had no luck. Turned out, I was running an old OS X (Sierra instead of High Sierra) and XCode (XCode 8.x instead of 9.4). I upgraded and then everything just worked.

[AugustoAleGon]

For anyone that is having the same issue. What I did was deleted the folder ios and then applied react-native eject.
And voila. react-native run-ios works!

[hramos]

Reiterating what Marc said at the start of the year. This error plainly indicates the project failed to compile or link. You'll need to look further up in your output for a hint of the root cause. I've opened #21303 in order to help people who run into this issue, and will lock this thread to avoid causing more confusion.

Duplicate of #21303