":CFBundleIdentifier", Does Not Exist #12737

alekseylovchikov · 2017-03-06T08:45:26Z

We use GitHub Issues for bugs.

If you have a non-bug question, ask on Stack Overflow: http://stackoverflow.com/questions/tagged/react-native

If you have a feature request, post it on Product Pains: https://productpains.com/product/react-native/

--- Please use this template, and delete everything above this line before submitting your issue ---

Description

react-native run-ios
then:

Installing build/Build/Products/Debug-iphonesimulator/pizza.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/pizza.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Additional Information

Version: react-native 0.42.0
trouble in iOS, android works fine
OS: MacOS 10.12.3

The text was updated successfully, but these errors were encountered:

ghost · 2017-03-06T09:08:02Z

Experiencing the same issue on 0.42.0

Kureev · 2017-03-06T12:16:11Z

Hi @alekseylovchikov!

Can you please check if your Info.plist is located at this path: build/Build/Products/Debug-iphonesimulator/pizza.app/Info.plist and have no syntax errors?

ghost · 2017-03-06T13:13:47Z

@Kureev I just checked and my Info.plist doesn't have any errors at this path.. the Info.plist isn't in /.app though - It's just in /Debug-iphonesimulator/

Kureev · 2017-03-06T14:23:18Z

I'm not the expert here, but I think it should be in the .app. Any ideas how it may happen?

Probably @grabbou can give you more insightful feedback on it

mrbone · 2017-03-08T15:24:24Z

@alekseylovchikov same issue, check your xcode version, if it's 7.2.1, you should update to xcode8.
For me it works.

alekseylovchikov · 2017-03-09T15:13:17Z

@mrbone xcode version 8.2.1

davidpelayo · 2017-03-14T08:49:26Z

same issue happening here.

macOS 10.12.3
react-native: 0.42.0
react-native-cli: 2.0.1

tjboudreaux · 2017-03-18T03:29:15Z

I'm having the same issue

macOS 10.12.3
react-native: 0.42.0
react-native-cli: 2.0.1

ytimocin · 2017-03-18T22:34:23Z

Same issue:

macOS Sierra 10.12.3
react-native-cli: 2.0.1
react-native: 0.36.1

Umity · 2017-03-20T13:29:44Z

same...
osx 10.12.3
xcode 8.2.1
react 042

Kureev · 2017-03-20T13:50:43Z

What do you have in "Bundle Identifier" here

and here?

Umity · 2017-03-20T15:53:49Z

com.myexample.myname
and
$(PRODUCT_BUNDLE_IDENTIFIER)

danilvalov · 2017-03-24T09:57:22Z

I have the same problem when I try to run my app using react-native (react-native run-ios --configuration Stage). I use a custom configuration for my Xcode project: Stage (except basic Debug and Release) and after the error I have a directory /ios/build/Build/Products/Stage-iphonesimulator with one subdirectory MyApp.app, but this directory is empty.

The Debug and Release configurations work correctly.
And also I can correctly build my Stage configuration using Xcode.

jjhesk · 2017-04-01T07:10:06Z

in my case I got this error from having the xcworkspace file saved in the folder ios and it stopped from using command react-native run-ios. I have this xcworkspace because it is required to have that from using fastlane to run another CI.

react-native run-ios
Scanning 804 folders for symlinks in /Volumes/RAMDISK/reactnative/gl/node_modules (107ms)
Found Xcode workspace onlyfastlane.xcworkspace
Launching iPhone 6 (iOS 10.2)...
Building using "xcodebuild -workspace onlyfastlane.xcworkspace -configuration Debug -scheme onlyfastlane -destination id=21C21FEE-A13E-43F3-9C61-E4EFFC98A46E -derivedDataPath build"
User defaults from command line:
    IDEDerivedDataPathOverride = /Volumes/RAMDISK/reactnative/gl/ios/build


xcodebuild: error: The workspace named "onlyfastlane" does not contain a scheme named "onlyfastlane". The "-list" option can be used to find the names of the schemes in the workspace.

Installing build/Build/Products/Debug-iphonesimulator/onlyfastlane.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/onlyfastlane.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

RN 0.42.3
XCode 8.2
Once I removed the workspace file and everything run as normal. Please fix that

rathierry · 2017-04-12T11:34:38Z

same issue happening here.

macOS Sierra: 10.12.3
react-native: 0.43.3
react-native-cli: 2.0.1

Please, help!!!!! :)

Kureev · 2017-04-12T12:49:34Z

I was looking around for any solution and found this thread. Maybe #7308 (comment) can help you solving this issue.

I propose to keep all discussions about :CFBundleIdentifier errors in one thread. Therefore, closing this issue in favor of #7308

agnellvj · 2017-05-11T08:42:38Z

I see the same problem as @alekseylovchikov. The error that is reported is that CpResource main.jsbundle failed to copy to the correct location. I have looked through every comment on issue #7308 and found nothing helpful since no one mentions that they had a problem with main.jsbundle. I tried running react-native run-ios --configuration Release but that fails too.

Building in Xcode also produces the same error.

Interestingly / annoyingly is that my coworker can build with no issues.

macOS Sierra: 10.12.3
react-native: 0.42.0
react-native-cli: 2.0.1

agnellvj · 2017-05-12T05:24:52Z

So, I borrowed a laptop from a friend and I get the same error as above. Just to reiterate, it has nothing to do with :CFBundleIdentifier the error occurs before that but it causes the build error when it tries to read the Info.plist in the build directory but of course it doesn't exist.

bz123 · 2017-05-22T08:05:31Z

react-native upgrade , get rid of your old ios files by letting it rewrite the pod files etc and you are golden.

Umity · 2017-05-22T08:43:28Z

how to get rid of old ios files?

On Monday, May 22, 2017, George ***@***.***> wrote: react-native upgrade , get rid of your old ios files by letting it

rewrite the pod files etc and you are golden.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.<

https://ci4.googleusercontent.com/proxy/ut9hJhU3jfu2KIEJrj6WzUr93hBZ6OF7beiCjV-piXSrw8X0x20Mjab-JS_bXFNtjLrQFEuSoix-RkUK5_h-S1ZhO3bV10L8_t7PwlPpq2nBtjcNhZynf_kAYyIm-DOprq_rJz5qtoZQN1z6oXWkKweec8iz9g=s0-d-e1-ft#https://github.com/notifications/beacon/AA6xMwboLcClc_uEBkC9UuSRj5UzLgjhks5r8UH-gaJpZM4MT3Tj.gif>

bz123 · 2017-05-22T08:49:10Z

@Umity react-native upgrade command will prompt you asking you if you want to change several files, just let it change them.

Umity · 2017-05-22T08:52:09Z

thank you George.. will try when home

On Monday, May 22, 2017, George ***@***.***> wrote: @Umity react-native upgrade command will prompt you asking you if you

want to change several files, just let it change them.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.<

https://ci3.googleusercontent.com/proxy/Jw4iN559fazhI7E1oDSPY0wu882nrigdja5wqbbJTjc_I5JPvj-obCbECh_gVcUQ89KRP5z6mybkI6voBRKpUDglsKIePCwMdexcamFc7ELMo-3jZkZWbWYIyQRTlFKyOvj0CGlJ30BxYxxtHYhYNcBLdR59ew=s0-d-e1-ft#https://github.com/notifications/beacon/AA6xMxwaHr3SwbOewjPquZjq0dpvGfpdks5r8Uw4gaJpZM4MT3Tj.gif>

alxvallejo · 2017-05-26T14:26:56Z

@bz123 That is not wise advice. Any previous custom configuration settings in your XCode project will be wiped clean. Proceed with caution.

MichelDiz · 2017-07-03T23:43:30Z

"React-native upgrade" command you'll lose a series of configurations. Must redo all by hand.
For me I did

React-native init TestSome (clean install see? but same result)
Install Xcode (latest)
Install it again (same result)
Install Xcode 9 beta 2 (same result)
React-native run-android = OKAY (just to garantee)
react-native run-ios --configuration Release = Noooops
But has ** BUILD SUCCEEDED **


** BUILD SUCCEEDED **


Installing build/Build/Products/Release-iphonesimulator/teste.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/Release-iphonesimulator/teste.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

No positive result ;-; (crying and losing hair)

RabbitJohn · 2017-07-09T04:03:33Z

I have got the same problem, and solved this problem by checking the console log and found this issue may be raised by another issue. the log has some errors: there is something wrong with the third-party:boost_1_63_0, and reports file not found, according this #14404 finally solved this problem by replace the boost_1_63_0 with the one I downloaded

nimishpatel19 · 2017-07-19T08:43:45Z

DO NOT use space in project path. It had solved my problem.

alopezc · 2017-08-02T02:14:54Z

same issue here, @nimishpatel19 is right, remove space in project path and all went ok

payamrafiee · 2017-08-03T14:35:33Z

@nimishpatel19 thanks man.... it solved my problem.

hramos · 2017-08-04T06:53:24Z

Duplicate of #14423

Kureev closed this as completed Apr 12, 2017

hramos marked this as a duplicate of #14423 Aug 4, 2017

facebook locked and limited conversation to collaborators Aug 4, 2017

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

":CFBundleIdentifier", Does Not Exist #12737

":CFBundleIdentifier", Does Not Exist #12737

alekseylovchikov commented Mar 6, 2017

ghost commented Mar 6, 2017

Kureev commented Mar 6, 2017

ghost commented Mar 6, 2017

Kureev commented Mar 6, 2017

mrbone commented Mar 8, 2017

alekseylovchikov commented Mar 9, 2017

davidpelayo commented Mar 14, 2017

tjboudreaux commented Mar 18, 2017

ytimocin commented Mar 18, 2017

Umity commented Mar 20, 2017

Kureev commented Mar 20, 2017

Umity commented Mar 20, 2017

danilvalov commented Mar 24, 2017 •

edited

Loading

jjhesk commented Apr 1, 2017 •

edited

Loading

rathierry commented Apr 12, 2017 •

edited

Loading

Kureev commented Apr 12, 2017 •

edited

Loading

agnellvj commented May 11, 2017

agnellvj commented May 12, 2017 •

edited

Loading

bz123 commented May 22, 2017

Umity commented May 22, 2017 via email

bz123 commented May 22, 2017

Umity commented May 22, 2017 via email

alxvallejo commented May 26, 2017

MichelDiz commented Jul 3, 2017 •

edited

Loading

RabbitJohn commented Jul 9, 2017

nimishpatel19 commented Jul 19, 2017

alopezc commented Aug 2, 2017

payamrafiee commented Aug 3, 2017

hramos commented Aug 4, 2017

":CFBundleIdentifier", Does Not Exist #12737

":CFBundleIdentifier", Does Not Exist #12737

Comments

alekseylovchikov commented Mar 6, 2017

Description

Additional Information

ghost commented Mar 6, 2017

Kureev commented Mar 6, 2017

ghost commented Mar 6, 2017

Kureev commented Mar 6, 2017

mrbone commented Mar 8, 2017

alekseylovchikov commented Mar 9, 2017

davidpelayo commented Mar 14, 2017

tjboudreaux commented Mar 18, 2017

ytimocin commented Mar 18, 2017

Umity commented Mar 20, 2017

Kureev commented Mar 20, 2017

Umity commented Mar 20, 2017

danilvalov commented Mar 24, 2017 • edited Loading

jjhesk commented Apr 1, 2017 • edited Loading

rathierry commented Apr 12, 2017 • edited Loading

Kureev commented Apr 12, 2017 • edited Loading

agnellvj commented May 11, 2017

agnellvj commented May 12, 2017 • edited Loading

bz123 commented May 22, 2017

Umity commented May 22, 2017 via email

bz123 commented May 22, 2017

Umity commented May 22, 2017 via email

alxvallejo commented May 26, 2017

MichelDiz commented Jul 3, 2017 • edited Loading

RabbitJohn commented Jul 9, 2017

nimishpatel19 commented Jul 19, 2017

alopezc commented Aug 2, 2017

payamrafiee commented Aug 3, 2017

hramos commented Aug 4, 2017

danilvalov commented Mar 24, 2017 •

edited

Loading

jjhesk commented Apr 1, 2017 •

edited

Loading

rathierry commented Apr 12, 2017 •

edited

Loading

Kureev commented Apr 12, 2017 •

edited

Loading

agnellvj commented May 12, 2017 •

edited

Loading

MichelDiz commented Jul 3, 2017 •

edited

Loading