I am getting very frequent crashes on XCode 6.01 especially when ever I try go to Source Control. I am using SVN.
Is there a workaround I could use ? Is this a known issue ?
It is probably related to the .xccheckout file.
If the project is a xcworkspace, it is located in the xcshareddata folder inside the xcworkspace bundle.
If the project is a xcodeproj, it is located in the project.xcworkspace folder in the xcodeproj bundle.
(The following trick seems to have fixed it for me:
quit Xcode
locate the .xccheckout file
revert this file to what is was when last saved with Xcode 5
reopen the Xcode project. If Xcode prompts for checking out the project from svn, do not press the ignore or cancel button, instead press the next button. In my case, it checked out another copy of my project from svn and the crash does not occur anymore.)
Step 1: Open terminal
Step 2: cd to your project's home directory
Step 3: Use commands below
http://www.linuxfromscratch.org/blfs/edguide/chapter03.html
Related
OS X Version 10.10.5
Xcode version 7.2.1
Very simple steps, yet Xcode can't fathom what to do when you duplicate a folder that contains an Xcode project.
Start with Xcode CLOSED.
Start with an Xcode project that builds and runs perfectly.
Go to Finder window and right click on the directory that contains the buildable Xcode project and hit "Duplicate"
New directory is created, called "SomeProject copy"
Go into this new directory and double-click on the SomeProject.xcodeproj file to open it in Xcode.
Bam... enjoy your build errors.
In my case, it's complaining about an enum.
Tried deleting derived data folder (did so directly using finder)
Tried super-cleaning the build folder by holding down the option key.
Tried removing and re-adding complained about file that contains errors.
Tried changing path to file in Xcode File Inspector from "Relative To Group" to "Absolute Path"
I should also point out that either Finder -> Duplicate doesn't actually do what it says it does. Neither does Finder -> Copy, ~OR~ Xcode for some reason has now adopted not only the original source location as where to get its build files, but also the new location, hence the "Redefinition" error. I noticed that if I open the "copied" project and edit a file, then go back to my original project in an entirely different folder, the file is changed THERE.
And my paths (according to Xcode File Inspector), are RELATIVE TO THE PROJECT IN QUESTION. So in other words, ProjectAAA's files are pointed to the path under ProjectAAA's directory, and the same with copied project, ProjectBBB's files.
So somehow, the copy/duplicate is refusing to actually copy/duplicate.
Any ideas how to solve this?
Per John Elemans comment, moving my original project then revealed in the copied Xcode project a number of build paths and issues that needed resolving. I fixed those, and it worked as expected.
I solved this issue as follows:
After duplicating the root folder of the project, open the podfile of the duplicated project:
Podfile
then comment all the previously added pods by adding "#":
Commented Pods
hit CTRL + S in order to save the changes
Open the terminal and change the directory to the folder of the duplicated project and then perform: "pod install". Yes it will delete all the pods but don't worry we will install again in the next step
Pods deletion
Open again podfile and uncomment the previously commented pods:
Uncommented pods
hit CTRL + S to save the changes
Open the terminal and change the directory to the folder of the duplicated project and then perform "pod install". it will install again all the pods:
Pods installation
Finally, run the Project and it should run without any problem.
I'm using xcode 6. Its fine to clean but it fails when I choose clean build folders.
Seems like you are restricted to create a build folder in your system root.
In XCode Menu --> Preferences --> Locations Tab --> Locations sub-tab, Change Derived Data to Relative and give any name in text box.
Have a look here which is also a permission problem in Xcode.
It could be due to Xcode bug (at least for me in Xcode 6.3.1). Toggling the location for derived data folder will fix it.
Go to Xcode > Preferences > Locations and change Derived Data to Relative, then back to Default.
Clean build folder again.
I just clean that folder in Finder, then all fine.
In Xcode 14 I clicked "Clean" command which had popped up in the 3rd row from the top and that fixed it.
When I create a new project in XCode 6.0.1, I got this error message: The file "exclude" doesn't exist
It seems to only impact the versioning of the files i.e. the generated stub files are not committed into github after the project is created.
What can cause this problem?
For me the issue was caused because I had previously created a project with the same name, and Xcode still had record of that.
To clear it out,
go to Window -> Organizer in the menu bar
Remove all of the repositories highlighted in red
To add your repository (if it's not being tracked for some reason),
Click the + (still in Window -> Organizer from the steps above)
Enter the path of your file
Make sure to change to Git from Subversion (if Xcode has Subversion set as default - it did for me.
I usually get this error if I initialize an Xcode project with a git repository, delete it and try to recreate it with the same name (casing doens't appear to make it sufficiently 'different'). Turns out, "Well I'll just start over" can leave some issues as well.
Hope this helps.
I had this issue as well, and I tracked it down to the .git-template folder included with Thoughtbot's dotfiles. Basically, Xcode expects its template folder to have info/exclude, and Thoughtbot's dotfiles don't. Creating that directory and file fixed the problem, as so (in the Terminal):
cd ~/.git_template
mkdir info
cd info
touch exclude
If you're getting this issue without Thoughtbot's dotfiles, you could probably look at ~/.gitconfig and use whatever templatedir is getting set as instead of ~/.git_template in the first command.
I where working with a project and I closed because my computer was geting slow. When I tried to open my solution again xcode quitted. So everytime I try to open my project I get this error:
I am not able to open my solution. IS THERE A WAY I CAN RECOVER MY PROJECT!?
Nothing mentioned above/below worked for me. Here's what I did instead:
Right click on the .xcodeproj file and select Show Package Contents. Then delete the project.xcworkspace file. Open the project in Xcode and voilà.
There are a couple of things you can try, first make sure Xcode is not running ,trash the ~/Library/Cache/ folder contents, and trash the contents of the ~/Library/Developer/Xcode/DerivedData/ folder, if you what to can just find the stuff for your project in ~/Library/Developer/Xcode/DerivedData/ and trash just that. Then restart your computer.
If that doesn't work, rename your faulty projects folder to so method like ' old', create a new project of the same name, and then move all of the source files from ' old' to you new project and add them. Its a bit painful I known but I have had to do this once to get a project working again.
Double click the actual file! NOT the recent item!
Turns out that double-clicking on the actual file instead of selecting it from the Welcome to Xcode window will help open the project as expected!
Also, after the first time open it with double-clicking the file, the window will be fixed by itself 🤷🏻♂️
In my case, the project was moved to my iCloud Drive without me noticing it.
If it happens to you too, just go to your Finder, locate the project and check if there is a cloud next to it. Just right click it and "Download now". Try again once the download is finished.
I was having this issue with Xcode 12. Opening Xcode, and selecting my project from 'Recent projects' list was causing Xcode to crash
My solution: I navigated to the folder and opened ProjectName.xcworkspace file, then it worked
If you're working with git, right click the project-name.xcodeproj > Show Package Contents, open the file project.pbxproj and check for conflict and resolve it.
Quit Xcode, then make a copy of the xcworkspace file (just in case). In finder, right-click the xcworkspace file and choose Show File Contents.
In that directory, open the xcuserdata directory and delete any contents. Start Xcode again and open the project.
In my case there was something wrong with the saved project state, so doing this resets the state and it opened normally.
I had the same error and none of the above helped me.
Solution that helped me: Create a new project, then without closing it, go to
File -> Open
and select your .xcworkspace file.
I recently upgraded to Xcode4 and noticed that my build/Release-iphoneos folder no longer gets populated with a .app or .dSYM file after I do a build.
**note - any build that is (build for running/testing/profiling). Also why is the build for archiving option gray'd out? in Xcode3 I was able to archive and build my .ipa w/ organizer
Am I doing something wrong or does the new IDE put a release build some place else?
Thank you in advance
By default it's placed in a new folder called 'Derived Data' within your Library folder. If you open up the preferences and go to the 'Locations' tab, you can change it back to the old location if you wish.
That is because Xcode 4 no longer uses that directory. If you look in preferences, you can both see where and change where Xcode 4 builds stuff.