Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
3 tasks
2ez4salt opened this issue Sep 22, 2018 · 11 comments
Closed
3 tasks

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

2ez4salt opened this issue Sep 22, 2018 · 11 comments
Labels
Resolution: Locked This issue was locked by the bot. Tech: Bundler 📦 This issue is related to the bundler (Metro, Haul, etc) used.

Comments

@2ez4salt
Copy link

2ez4salt commented Sep 22, 2018

Environment

React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
Memory: 40.32 MB / 8.00 GB
Shell: 3.2.57 - /bin/sh
Binaries:
Node: 10.10.0 - /usr/local/bin/node
Yarn: 1.9.4 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
IDEs:
Android Studio: 3.1 AI-173.4907809
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
react: ^16.3.0 => 16.3.0
react-native: ^0.57.1 => 0.57.1
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1

Description

developing app with RN,i can see my app on expo, it builds well , but when i want publish my app i need my "appname.xcodeproj" and its giving me on compiling 1600 errors. when used "react-native run-ios" thats giving me :

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

@react-native-bot react-native-bot added the Tech: Bundler 📦 This issue is related to the bundler (Metro, Haul, etc) used. label Sep 23, 2018
@react-native-bot
Copy link
Collaborator

It looks like you are using an older version of React Native. Please update to the latest release, v0.57 and verify if the issue still exists.

The ":rewind:Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.

@2ez4salt
Copy link
Author

2ez4salt commented Sep 23, 2018

Update

React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
Memory: 822.98 MB / 8.00 GB
Shell: 3.2.57 - /bin/sh
Binaries:
Node: 10.10.0 - /usr/local/bin/node
Yarn: 1.9.4 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
IDEs:
Android Studio: 3.1 AI-173.4907809
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
react: ^16.3.0 => 16.3.0
react-native: ^0.57.1 => 0.57.1
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1

Description

i updated my development enviroment

and now
Talha-MacBook-Pro:TusTTS talhasalt$ sudo react-native run-ios 03:12:29: Starting packager... 03:12:38: Starting simulator...

its stucks here

@2ez4salt
Copy link
Author

2ez4salt commented Sep 23, 2018

Update

I updated my react-native package to last version.

if i write
sudo react-native run-ios
it says
03:43:31: Starting packager... 03:43:41: Starting simulator...

and its stucks here

and if i write firstly

Talha-MacBook-Pro:TusTTS talhasalt$ sudo react-native eject

then

sudo react-native run-ios

adsiz

@alexandrius
Copy link

alexandrius commented Sep 23, 2018

This may sound super weird but the issue resolved after I removed react-native-maps and then installed it again. Might be coincidence

@arifrhkim
Copy link

I've got the same error here, is this issue come from the version of xcode ?

@2ez4salt
Copy link
Author

I've got the same error here, is this issue come from the version of xcode ?

i dont think so cus i had this issue on old xcode

@ChrisXu
Copy link

ChrisXu commented Sep 24, 2018

@2ez4salt , Are you able to open the project in Xcode? It seems like the project setting is damaged

@rottenoats
Copy link

I created a fresh project and have the exact same thing occuring.

React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
      Memory: 182.57 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 8.12.0 - /usr/local/bin/node
      Yarn: 1.9.4 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
      Android SDK:
        Build Tools: 23.0.1, 23.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.3
        API Levels: 23, 26, 27
    IDEs:
      Android Studio: 3.1 AI-173.4670197
      Xcode: 10.0/10A255 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.5.0 => 16.5.0
      react-native: 0.57.1 => 0.57.1
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

@lovegrovegeorge
Copy link

lovegrovegeorge commented Sep 24, 2018

Just my two cents on this, i've tried every idea from multiple issues on the XCode 10 update but none worked.

My work around for the meantime was to delete XCode 10, re-download 9.4.1 from https://developer.apple.com/download/more/ install and restart. Make sure to double check the command line tool is 9.4.1 in XCode => Preferences => Locations => Command line tools.

My project still didn't work after doing that so I tried downloading another copy of my project from github, npm installed and added env files and then this did build. Doubled checked the original project folder again and this still didn't work even running it in XCode 9.4.1. XCode 10 may have changed the XCode file itself which for the meantime is broken (at least I couldn't find a solution for now).

@hramos
Copy link
Contributor

hramos commented Sep 24, 2018

The Print: Entry, ":CFBundleIdentifier", Does Not Exist message is sort of a red herring. This line of text will always print out whenever the project fails to launch for whatever reason. This is very confusing as developers tend to bundle "CFBundleIdentifier" failures into one, which makes it hard to find actual workarounds.

For anyone who ends up here because of a "CFBundleIdentifier" error, please look back through your logs as the actual failure most likely happened earlier in the build process.

@hramos
Copy link
Contributor

hramos commented Sep 24, 2018

Duplicate of #21303

@hramos hramos marked this as a duplicate of #21303 Sep 24, 2018
@hramos hramos closed this as completed Sep 24, 2018
@facebook facebook locked as resolved and limited conversation to collaborators Sep 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Sep 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot. Tech: Bundler 📦 This issue is related to the bundler (Metro, Haul, etc) used.
Projects
None yet
Development

No branches or pull requests

8 participants