-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
[Master Task] Print: Entry, ":CFBundleIdentifier", Does Not Exist #14423
Comments
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 |
@srijak I also come across this error , Im trying your solution now |
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. |
+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. |
Summary: This is to help debug the root cause of #14423 Reviewed By: javache Differential Revision: D5254713 fbshipit-source-id: 1ca90205144b3a069d927ba6636f0ef0138b51a0
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. |
I thought I've figured out how to fix this problem.
So, I did the following steps:
|
I had this issue too, but it disappeared once I used |
Temporary SolutionDownload boost_1_63_0.tar.gz to |
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: My build process would just error out and stop, giving me:
I then deleted the |
Fixed by removing everything from ~/.rncache/ |
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 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. |
I had this issue too, but it disappeared once I removing everything from ~/.rncache/ and used command react-native-git-upgrade |
Reinstall node_modules |
Have this issue been resolved? Still encounter this issue with |
My belief is that somehow the files in ~/.rncache/ are corrupted, and so unpacking them doesn't work right, but for some reason the error is not caught. https://github.com/facebook/react-native/blob/master/scripts/ios-install-third-party.sh will not re-download those files once they exist in ~/.rncache/. If you're running v0.47.0-rc.0 or newer, the debug info at line 22-24 may help confirm. I believe at this time the correct fix is for the ios-install-third-party.sh script to encode the sha hashes of the files which it will download, and verify the contents of ~/.rncache/ against them before using them. If the hashes don't match, It can retry the download a few times. This should fix the problem for good. If someone wants to work on this, that would be awesome, or else I will do it when I can. For now, the workaround is to |
I downloaded the library boost_1_63_0.tar.gz, replace it in ~/.rncache/ and extract it in /node_modules/react-native/third-party/boost_1_63_0 and it worked. |
My fix was a match of some of the above mentioned solutions: |
This article would be helpful : Handling third party build error on react-native 0.46x |
i have try many ways, but no ways |
Duplicate of #14447 |
I have the same issue. Thank you for the response. |
@HazT I guess you have to create new workspace. Do the same thing again & create a new project/workspace. Make sure you have closed Xcode. |
@apppro123 the |
Thank you. now I have found it. |
I have tried with the new workspace and done the same things with closed Xcode but still throw below error: _Installing build/Build/Products/Debug-iphonesimulator/AwesomeProject.app An application bundle was not found at the provided path. Print: Entry, ":CFBundleIdentifier", Does Not Exist Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/AwesomeProject.app/Info.plist |
I also still struggle with it: he following build commands failed: (1 failure) Installing build/Build/Products/Debug-iphonesimulator/OwnAppIOS.app Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/OwnAppIOS.app/Info.plist |
I managed to fix the problem for myself (Not sure if everyone else is facing the same situation though) TL;DR The fix is to ensure environment variables are present in the build log Yeah, I know you are like 🤯. I am too. Let me explain a little more. So based on the following error I figured that the
When I went into the folder rightfully so,
Basically the name is being read from an environment variable
This explains why removing |
this is really weird, every time when i face that error, i am fixing with different suggestions, one time fixed with @dotmike and @sheminusminus, and this time I solved @barbatus suggestion and run react-native-git-upgrade on the terminal |
There are several info.plist files in my ios directory. Which one needs to have a reference to the CFBundleID? |
xcodebuild: error: Unable to find a destination matching the provided destination specifier: run |
It's not working, nothing is working |
I found this issue may come out if 8081 port is occupied(In my case it is occupied by McAfee). |
so this issue has plagued me forever What I did to fix mine is, run it in xcode and look at the error xcode outputs
I hope it helps a little:) |
I had a problem related to glog-0.3.4 not finding a file named "config.h" and it was causing the CFBundleIdentifier error. Solved it with this steps:
My project is a standard |
在 2018年8月8日,下午10:05,Omkar ***@***.***> 写道:
It's not working, nothing is working
I'm losing my faith in react-native now
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#14423 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZLspyrgvAacqpqPWPbSVFTPtIYfg365ks5uOvBGgaJpZM4N1cxv>.
This problem maybe cause of your react-native javaScript code incorrect , do not about the CFBoundleID , please keep the enthuasiasm of react-native
|
For what it's worth, I can't get this working for a completely blank project. |
@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 |
@williamdarkocode thank you but that didn't fix it. Literally a vanilla project won't build. |
Same problem using ignite latest versions of everything... |
If anyone still having the same problem, after running all the proposed methods to no solution, I found that
|
@HazT try with |
Heres what I did
And it worked perfectly, first time. |
run in your terminal: killall -9 node That solved it for me! |
I was getting 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. |
For anyone that is having the same issue. What I did was deleted the folder |
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 |
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:
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:
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.
The text was updated successfully, but these errors were encountered: