-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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 #14447
Comments
@thiagovictorino I was able to fix by doing 'npm start' or 'npm run ios' instead... there seems to have been changes in version 0.45 |
Having the same issue here. However, doing |
Thank you @Mikael491, but it didn't works =( |
@thiagovictorino It looks like you just created the project, try doing 'npm install -g create-react-native-app' and then creating the project with 'create-react-native-app ' like in the docs...this is how I began my solution |
Hi @Mikael491! This open the new project, but in a very different folder structure (very lean) and with 0.44 react-native version. It could be a partial solution and I am grateful for your help. But I need a Native Code, and I used the command with no success
|
I have the same issue. -> 'react-native init ...' But I have really serious problem. |
Can you confirm that 0.45.1 is being used here? The issue you're describing was present in 0.45 but should have been fixed. |
Hello @hramos, yes it is
|
react-native 0.45.1
|
When I run ios-install-third-party.sh got this error
Finally running react-native run-ios again I got the same error:
|
@phuwasit your solution doesn't help me. |
@radko93 @thiagovictorino
|
+1 |
I have the same problem and provided solutions didn't work for me. Xcode 8.0, React native 0.45.1 |
same problem with react native 0.45.1 |
This is one of seemingly many factors but at the very least make sure your project folder or any of the folders it's within from ~/ down don't have spaces in them |
Same here and no space in path! |
My RN project works fine locally. When I push it to git and then pull it down. npm install and link all libraries. I cannot run the project because of CFBundleIdentifier does not exist. |
Devs keep ignoring this issue, and keep closing them. My Faith in RN is loosing momentum. |
As you can see at my question @SamMatthewsIsACommonName I have no space in my path
|
I had the same problem and it turned out to be a matter of updates. I had a pending update of macOS Sierra to version 10.12.5, I did it and now it works. |
react-native-cli: 2.0.1 Still not working |
@RooneyJung My project same to your's |
@thiagovictorino Check your node_modules/react-native/third-party file,normal size is 160M.For some reason,this file can't download full version can cause this problem.I copy this file from others,replace,problem solved. |
e first , check your permission of manager sudo chmod -R 777 yourdirname . |
Same error after downgrading the react native version on my system but on the another system working properly, what the issue, I can't figure out, Is this going to fix or not? |
@whg1412 my |
@isuhendro You can get it here https://github.com/whg1412/ThirdParty. I copy it from others,solve my problem. |
I had this issue today and I figured I was using an old version of Node JS. Try upgrading it. |
I am having this issue now: None of the solutions I've seen (removing spaces in path; changing relative build location) have worked. |
@dgurns I added the third part files manually and it worked. |
@GabrielLidenor what versions of React Native, MacOS, Node, and XCode are you running? I tried adding the third-party files manually but it didn't work. What steps did you follow? |
@dgurns Well, first of all I updated my Node JS to the latest version available. After that I created a new project using the latest version of React-Native and then, I replaced the third-party folder. |
Closed the wrong issue - let's leave this one open as the master issue. |
I just merged several related issue. Let's avoid opening new issues for the same error message for now. It seems like the preferred workaround at this time is to do the following:
Wait for the last command to finish in its entirety. You should see several messages that follow this format: Thanks to @jjerryhan for arriving at the above list of steps (see Handling third party build error on React Native for an explanation behind why some people may end up in this state). I believe I saw some PRs land recently that may deal with this particular issue, but I'm not 100% sure. I'll come back and update this issue with my findings. To aid in the investigation, please refrain from adding "me too" comments unless you have new information to share. |
It looks like @mhorowitz has looked at this before (see a555551 and his comment on #14423). If you see the following message, "Unpacking 'SOME_FILENAME_HERE' failed. Debug info:", when running Since Marc has already commented over at #14423, I'll mark that as the canonical issue and point all other issues there. Sorry for the churn. |
Duplicate of #14423 |
I replaced the third-party folder with this https://github.com/whg1412/ThirdParty as @GabrielLidenor sad and it worked for me too. |
Having this issue again, none of the above worked. react: 16.0.0-alpha.12 I have another project using react-native 0.44.0 and perfectly works, but when I tried to create a fresh one I'm having this issue. |
downgrade method can't work either, after trying all these so called solution, i finally decide to use my ultimate method that is to "wait", these stuff is too time consuming. |
this works for me. |
I am trying to run a new react-native project but I have an error
My setup
I tried everything that others similar issues say:
If I try to compile in xcode, I had this problem
And I just run the react-native init projectName and react-native run-ios the get this error
Have anyone a modern (2017) solution for this problem?
The text was updated successfully, but these errors were encountered: