2

Error Code

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

To be solved

I want to start up an iOS simulator.

The actual device is iOS 14 and I upgraded Xcode in order to build the actual device.

As a result, the simulator doesn't work and I tried many things, but it didn't work, so I'd like to hear advice from someone who knows how to solve this problem or who has been in the same situation.

My environment.

  • npm 6.14.7
  • node 14.9.0
  • react 16.12.0
  • react-native 0.61.5

What I tried

  • Remove iOS/build.
  • Clear the pod cache.
  • Check whether the port used by react-native is already in use.
  • Quit the iOS simulator.
  • Restart the PC.
  • Build with Xcode (I couldn't).
shim
  • 9,289
  • 12
  • 69
  • 108
taizo
  • 77
  • 1
  • 8

1 Answers1

1

TLDR - delete yarn.lock and run yarn.

I had this same issue when upgrading to Xcode 12. I first followed this post to make React Native compatible with Xcode 12 Problems after upgrading to Xcode 12:ld: building for iOS Simulator, but linking in dylib built for iOS, architecture arm64.

My project could then build with Xcode, but not the react-native cli. react-native run-ios threw the error Print: Entry, ":CFBundleIdentifier", Does Not Exist Removing my yarn.lock file and running yarn did the trick as the new cli version has updates to this problem - https://github.com/react-native-community/cli/issues/1235.

Craig1123
  • 1,510
  • 2
  • 17
  • 25
  • OK, I'll try it. Thanks – taizo Sep 30 '20 at 03:16
  • FYI: For those like me who find this post years after it originated, please note that it's now standard practice to decouple the cli from your app. This means that `@react-native-community/cli` is no longer part of my package.json. I mention this because, although I run commands with `npx`, I still get this same error as noted in this post. Still haven't figured out why. – Mike S. Feb 18 '22 at 17:01