Closed
Description
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:
- Upgrade to the latest React Native release.
- Upgrade to the latest Xcode version.
- Read through the Getting Started guide if you haven't in a while, and make sure your development environment is up to date.
- 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.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
hramos commentedon Jun 9, 2017
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 commentedon Jun 10, 2017
@srijak I also come across this error , Im trying your solution now
it's OK now, tkx :)
kyle-ssg commentedon Jun 10, 2017
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.
haseebyf commentedon Jun 12, 2017
+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.
Add some debug logging if tar fails
mhorowitz commentedon Jun 15, 2017
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 commentedon Jun 21, 2017
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).So, I did the following steps:
.sh
, put it in the~/.rncache/
.node_modules/react-native/third-party/
, rantar -zxf ***
to each file.barbatus commentedon Jun 26, 2017
I had this issue too, but it disappeared once I used
react-native-git-upgrade
for the upgrade.iineva commentedon Jun 29, 2017
Temporary Solution
Download boost_1_63_0.tar.gz to
~/.rncache/
, replace if exist.PaulAndreRada commentedon Jun 30, 2017
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:
I then deleted the
ios/
andandroid
/ folders and didreact-native eject
then triedreact-native-git-upgrade
for the thousand time, and it worked!folivi commentedon Jul 4, 2017
Fixed by removing everything from ~/.rncache/
m-bigaignon commentedon Jul 11, 2017
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 react-native@0.46.1, but not with react-native@0.45.0.
178 remaining items
messiBob commentedon Aug 24, 2018
sonnytron commentedon Aug 30, 2018
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 commentedon Aug 30, 2018
@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 commentedon Aug 31, 2018
@williamdarkocode thank you but that didn't fix it. Literally a vanilla project won't build.
heberuriegas commentedon Aug 31, 2018
Same problem using ignite latest versions of everything...
heyjoy21 commentedon Sep 10, 2018
@HazT try with
sudo
Tak783 commentedon Sep 11, 2018
Heres what I did
react-native init myAppName
cd myAppName
npm install
react-native upgrade
react-native link
And it worked perfectly, first time.
Was able to run iOS from xCode
ferdelamad commentedon Sep 14, 2018
run in your terminal: killall -9 node
That solved it for me!
jeremyis commentedon Sep 16, 2018
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 commentedon Sep 19, 2018
For anyone that is having the same issue. What I did was deleted the folder
ios
and then appliedreact-native eject
.And voila.
react-native run-ios
works!hramos commentedon Sep 24, 2018
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