Skip to content

[Master Task] Print: Entry, ":CFBundleIdentifier", Does Not Exist #14423

Closed
@srijak

Description

@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.

Activity

hramos

hramos commented on Jun 9, 2017

@hramos
Contributor

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

WhoJave commented on Jun 10, 2017

@WhoJave

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

kyle-ssg

kyle-ssg commented on Jun 10, 2017

@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.

haseebyf

haseebyf commented on Jun 12, 2017

@haseebyf

+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

mhorowitz commented on Jun 15, 2017

@mhorowitz
Contributor

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

pampang commented on Jun 21, 2017

@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

barbatus commented on Jun 26, 2017

@barbatus

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

iineva

iineva commented on Jun 29, 2017

@iineva
Contributor

Temporary Solution

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

PaulAndreRada

PaulAndreRada commented on Jun 30, 2017

@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

folivi commented on Jul 4, 2017

@folivi

Fixed by removing everything from ~/.rncache/

m-bigaignon

m-bigaignon commented on Jul 11, 2017

@m-bigaignon

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.

193 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @srijak@folivi@apsuva@codler@abmirayo

        Issue actions

          [Master Task] Print: Entry, ":CFBundleIdentifier", Does Not Exist · Issue #14423 · facebook/react-native