Related
I'm using Xcode Version 6.4 (6E35b)on a mid 2013 MacBook Air running OS X 10.10.5.
A few days ago, with my code in something of a tangle, Xcode crashed. After the crash, my app built and ran, but didn't do anything except eat memory at a fantastically fast rate.
I keep a git repository and every now and then a put a copy of the whole project folder on an offsite location.
I got one of my older versions out of storage, did a build and run and the same thing happened.
All copies of the same project (by name) now do the same thing. Run, eat memory, and nothing else.
I tried removing DerivedData, removing contents of /var/folders/, removing and replacing schema (in schema -> manage), removing all projects, emptying trash, and have removed Xcode (using "trash me") and reinstalling. No joy. Still the same thing.
I was wanting to change the name of the project anyhow, so I changed the name, and it works. Unfortunately, I can't seem to change the name of the folder containing the project. Using the file inspector, I'm able to change the names of almost everything, but info.plist wants to keep an extra copy of the old project folder name in it's path, as far as DerivedData and LLVM are concerned.
Right now I will continue working with the old project folder name, but new project name.
How do I make Xcode forget the old folder name?
As edited by John Caswell, the answer is basically covered by a careful reading of Duplicate and rename Xcode project & associated folders. I'm going to close this and resubmit the parts of the question that aren't answered.
This is a long one, but please, bear with me. I really need help here.
I use Eclipse (latest version) to play with some programs of my own. During installation (?), it asked me where I'd like to put in my Workspace folder. I set it to default, but, not wanting to dig through Documents and such (I have my own Documents folder on another drive), I made sure that every project I have is condensed into one "Projects" folder, not in the Workspace. My "Projects" folder contains every program I've coded so far, from C# to Java, as well as the necessary tools, like the Eclipse folder.
It worked fine for me, until I decided I want to do another project. So, I navigated to my "Projects" folder, and then created it there.
Now for some reason, Eclipse treated the directory I navigated to as my project folder. As in, new folders like bin, src, etc. started popping up in my otherwise organized folder. Visual Studio does not have this problem, and actually creates a new folder for your project under whatever directory you set it to.
So I, in a 'Monday blues' move, went into Eclipse and deleted my project. Eclipse wasted no time in deleting my entire "Projects" folder and everything in it - including itself, apparently. Gah.
I quickly closed Eclipse, but it kept saying something about 'Saving Workspace' which I assumed meant "Don't close me yet, I'm still deleting your files."
I thought I was being sensible when I terminated it via the Task Manager. It stopped deleting my stuff, but out of the dozen or so programs, I only managed to save three.
Wanting to start over again, I deleted (what's left of) my Eclipse, so I can 'install' it again, and let it have its way of where to create projects and save my files, so that this doesn't happen again. Unfortunately, one folder keeps returning no matter how many times I delete it. The aforementioned bin folder, a name that needs at least two adjectives and the suffix "Of the Damned."
So, to summarize:
I lost majority of my programs.
I lost my Eclipse.
And folder 'Bin' keeps popping up.
And so I'd like to ask:
Can I recover my files?
How can I setup Eclipse so that it creates a new project folder when I create a new project instead of treating the directory as the project folder?
How can I permanently get rid of that haunted Bin folder?
If anyone an help out here, thank you so much. This has easily been one of my worst Mondays.
As of now, I have tried:
Restarting my PC (didn't work, Bin Folder is still there)
Downloading and running a new copy of Eclipse (didn't work either)
I have struggles also on my Eclipse for the past few weeks. I answer each of your question below, hope that helps.
Can I recover my files? - If your programs are not physically removed from disk, you can add it back when you have your Eclipse running
How can I setup Eclipse so that it creates a new project folder when I create a new project instead of treating the directory as the project folder? - Create your project by clicking File->New->Android Application Project (if android). Then input the application name,etc. Click Next and uncheck create project in workspace, from there you can have your own location or directory of your project.
How can I permanently get rid of that haunted Bin folder? - In may case, I downloaded a fresh copy of Eclipse. I used the adt bundle which can be downloaded here: http://developer.android.com/sdk/index.html
the sad news is, that Eclipse does not just delete the projects into the bin, like it would happen with the "delete" by clicking on the folder and manually deleting it. You could try with recovery software, but it is not an assurance it will work, or recover all your lost data.
For the more of it, in the Bin folder that is made automatically in any Java project, you get compiled classes which are what gets packaged/archived into any jars that are created.(I hope this makes sense, I couldn't find a better way to explain myself.)
For the set-up of Eclipse I would have a look at the page of Eclipse, maybe a forum, or a FAQ is there.
I for instance use Netbeans, which does from the start always create a new folder for the new projects.
I hope I could somehow help!Here a little link to a recovery software that has a good reputation: http://www.piriform.com/recuva
Kind regards,
DomExtra edit: Version Control is an awesome tool to save your buttex from trouble like this ;)
I have used Eclipse and Apatana for years on Linux, but have recently switched to Windows 7 in order to be compatible with my business partners. I have installed the 'Aptana Studio 3.4.0 Microsoft Windows, x86' standalone version of Aptana, and after install it runs great until I close it. When I try to re-open it, it hangs ('not responding' message) and I have not found any way to resolve the issue other than deleting the .metadata directory in my aptana workspace, which of course deletes all my project references, deployment settings, and any other tweaks I've made to the app, and setting this back up every time I restart the app is a waste of my time. Can anyone identify the problem? I have a pastebin of my log at:
http://pastebin.com/2J0AWTNR
Any help would be greatly appreciated!
instead of deleting the whole .metadata, you can try to delete the .markers file for any open project:
in this folder:
...\.metadata\.plugins\org.eclipse.core.resources\.projects\[myProject]
Delete (if it exists), then add an empty .metadata folder inside your project directory.
I had the same problem on Windows 7, Aptana hanging for eternity on startup.
Following posts like this one I looked for the .metadata folder inside the project directory but didn't see any there.
I tried creating an empty .metadata folder in the project directory, and Aptana started up.
Have had the same problem and I've reinstalled which makes no difference. So I deleted the .metadata/.plugins/org.eclipse.core.resources/.projects folder and it fixed it and with no settings/data etc loss amazingly :-)
I used this fix at first and then ran into more problems after a while. The sidebars and other objects in the program were not working and as a result the program just stopped responding. I have finally found a fix here http://youtu.be/RYobTLq_hms?list=UUtL_0WLPWmHZE_HcX48F96w and I hope that this helps for all! We can finally get back to work!
I wouldn't call the following a fix, but it helped me so here it goes:
My Aptana didn't start. It would just hang and when you click anywhere in the blank screen Windows would say the program isn't responding...
This is what "fixed" it for me:
Navigate to: C:\Users\YOURNAME\Aptana Studio 3 Workspace\
Create a new dir and move the ".metadata" dir into it.
Start Aptana
Aptana will run now, but all your projects will be gone.
Remove the new ".metadata" directory that Aptana just created at startup.
Move the ".metadata" folder out of the one you just created, back to its
original location.
Now run Aptana again.
This fixed my problem.
All of a sudden my project fails to build in Xcode. If I look at the log I see all the needed dependencies being built, and then I get a strange error:
Verify final result code for the complete build operation
Build operation failed without specifying any errors.
Individual build tasks may have failed for unknown reasons.
I removed my code directory and replaced it with a backup, did a clean, tried building all the other components separately (they succeed) - nothing works. I tried a command line build, same issue.
There were only a few hits on google for this error, none offered any useful advice.
Can anyone please help?
Update: When I run the command line build, I see the following error:
2012-05-25 08:55:53.830 xcodebuild[3358:4203] No recorder, buildTask: <Xcode3BuildTask: 0x400f35e60:'ProcessPCH MyProject-Prefix.pch':REfc(32370056113422336):deps=0:phaseNum=4>
I checked the output of xcodebuild and it is returning '65'.
I thought there might be a problem with the MyProject-Previx.pch file, so I shut off "Precompile Prefix Header", and now I get the same error with a different file:
2012-05-25 09:15:11.784 xcodebuild[3882:3703] No recorder, buildTask: <Xcode3BuildTask: 0x40048ab60:'CompileC HelperRoutines.m':REfc(33777199068741632):deps=0:phaseNum=4>
Build operation failed without specifying any errors. Individual build
tasks may have failed for unknown reasons. One possible cause is if
there are too many (possibly zombie) processes; in this case,
rebooting may fix the problem. Some individual build task failures (up
to 12) may be listed below.
I've run into this problem consistently recently while running Xcode 9.0 Beta 3 and Xcode 8.3.3.
The fix is to delete ALL in the Derived Data folder. It then seems to work again.
rm -rf ~/Library/Developer/Xcode/DerivedData
NOTE: just cleaning the build or deleting the current build folder for a project does not seem to help.
Hope this helps :)
I was hitting this error and it infuriated me for an hour or so. The answer below helped me out a lot: essentially your machine has a ton of running processes, XCode can't handle it, and rebooting your machine is the best answer.
https://stackoverflow.com/a/13183522/1863655
I looked around for a bit and the only one that worked for me was shortening my project folder name.
All other tries: restarting, recloning, deleting derived data, etc. didn't work. The only thing that worked was making the project folder name shorter.
I also encountered same error. I was edited .pch (Prefix Header) file. Then I started getting this strange error.
Then I removed all editions which I made in .PCH.
Then I quit my Xcode.
When I restarted Xcode this strange error was gone.
Hope this will work for you also.
Best luck Buddy (y)
Build operation failed without specifying any errors. Individual build tasks may have failed for unknown reasons.
One possible cause is if there are too many (possibly zombie) processes; in this case, rebooting may fix the problem.
Some individual build task failures (up to 12) may be listed below.
This happens occur when the total path length is too long.
change the folder name or location of directory, shorter then before.
Happy 2019, everyone, but sad to say this can still happen in Xcode 10.2.
I had four projects open in Xcode but only one failed in this way. I tried a main menu > Product > Clean Build Folder. The little progress spinner started up and 5 minutes later was still spinning. Hmmmm.
So I quit Xcode and in Terminal did a cd ~/Library/Developer/Xcode/DerivedData. Although ls -alww showed only one subfolder named after each of my other projects, as expected, there were five subfolders whose name began with the name of the problem project. I deleted all of them
rm -R ProblemProjectName-*
and relaunched Xcode. Problem solved.
Mine gave this error sometimes, also LLVM failed with exit code 1 and clang failed with exit code 255, at different code locations each time. I just had to reboot (OS X 10.7, Xcode 4.5).
I rebooted, no luck. Then I noticed that when I relaunched XCode, one of my tabs was loaded with no file in it. I figured out what file I was editing in it, opened it, saved it and then I was able to build.
None of these answers worked for me on XCode 5.
Luckily, I'm still only testing XCode 5 - I kept XCode 4 around.
XCode 5 simply won't build one of my two projects, claiming that my libraries aren't built with the right settings, and I keep running into the error described on this page on the other one... so I'm sticking with XCode 4, which builds both of my projects perfectly well.
If you are experiencing this issue on XCode 5, consider "reverting to XCode 4" as another strategy.
Overall the idea that repeatedly running a program, XCode or not, degrades your system to the point where you have to reboot does not fill me with confidence in that program.
With Xcode 5.0.0, this error was caused after an update to the CLI tools.
Updating to Xcode 5.0.1 and installing all the required components again still didn't fix the error. However, 5.0.1 was kind enough to actually emit an error that was useful.
/bin/mkdir -p /Users/xxx/Documents/XCode/SampleApp/bin/SampleAppDebug.app/Contents
error: (null)
This lead me to look at the bin folder, and find out that the 5.0.0 build with broken CLI tools had made a symlink in bin/ to the derived information folder with SampleAppDebug.app, which for some reason it could not write to.
I manually removed all contents of the bin/ folder and rebuilt without errors.
I faced same problem. I have change my System time.I delete file "/Users/YOURNAME/Library/Developer/Xcode/DerivedData/ModuleCache/YOURBUNDLEID/UIKit.pcm". Then it's work fine for me. Try this.
I added into the Framework search paths the header file location.... removing this from the top level project settings fixed the issue for me.
Change at your peril.
The only workaround, that works for me - push your code to git repo and clone it to new location.
I highly recommend to reclone your repo, because you'll deal with some random problems if you prefer rebooting/turning off and onXcode.
did you set "Perform Single-Object Prelink" to Yes?
try turn it off.
i had the similar problem. i have tons of files in a static library. reducing the number of files or setting "Perform Single-Object Prelink" to NO solved my problem.
Same error and following didn't work for me for Xcode 6.3.2 on Mac OS X Yosemite 10.10.3:
Git discarded changes to last successful build point
Creation of new fresh project from scratch from a builtin template (though I cannot recall whether it built successfully or not)
Restart of Xcode
System Reboot
and the following worked:
I faced the problem in the morning and it got resolved in the evening with a couple of Xcode restarts and System reboots and creation of new project. So, I'm not sure what really triggered.
I faced the same problem today. Cleaning the DerivedData and cloning the project somewhere else didn't help. What fixed my problem was repairing the volume from the Disk Utility app and removal of all Xcode plugins.
I have encountered same issue without having any code changes for my project running on Xcode 9.2. It looks like if you have some run scripts or external build systems attached to the project, this might cause an issue. Try committing or discarding changes and build again. If it still persist, delete local repo and clone again. Also maintain smaller folder names for project location.
Same issue when added watchOS target inside iOS app, using Xcode 11.1 with SwiftUI:
Go to menu Xcode / Preferences / Locations
Open Derived Data folder in Finder clicking on the arrow next to /Users/yourUserName/Library/Developer/Xcode/DerivedData
Locate your app Derived Data folder and delete it
Menu Product / Clean Build Folder
You should be able to compile again.
I know this is super late to answer but I'm answering since none of the above solutions worked.
For me restarting, clean building, deleting derived data nothing worked.
Because the issue was not due to any zombie objects or something like that.
I'm using Xcode 11. I think it's an Xcode bug that sometimes errors are not shown in the issue navigator. But don't worry check the build report in Report navigator(The last tab in project navigator: the one that looks like a comment box with lines in it. or simply cmd + 9).
Click the relevant build and resolve the issue, mine was missing file in pods directory.
just try to rename the folder name of the project. it did the trick for me
I had this same problem, however the accepted solution did not work for me, what worked was:
deleting .workspace file
deleting Podfile.lock file
deleting the Pods folder
pod deintegrate ; pod install
For me it was fixed by changing to the new build system(in File -> Project settings)
I have Xcode 11.7
Indexing, code completion, & coloring disappear from my projects on a fairly regular basis, usually right after I add a file. And then it returns hours or days later, usually for unknown reasons (I've tried keeping a record but it's pretty random). CMD-clicking on even known terms (like viewDidLoad: or NSLocalizedString) result in a "Symbol Not Found" error.
It happens with Xcode 4.2 (I believe it happened in Xcode 4.0.2, but not as frequent).
I have no build errors, warnings, or static analysis messages.
I've restarted Xcode.
I've tried turning precompile off.
I don't have a case where I've got a circular header file include/import.
It happens if I use gcc, LLVM, CLang (in whatever combo).
It happens if I use iOS 4.3 or 5.0.
I've tried deleting the "derived data.", and even only the Index/ path.
After deletion & re-build I see the .hmap file & .xcindex folder (filled with db.xcodeindexdb* files).
...but I can't get code-completion, symbol detection, or coloring back.
What else can I do? I sincerely appreciate the help.
Have you tried a clean install (sudo /Developer/Library/uninstall-devtools)?
I have exactly the same problem for one particular project. Following workaround works for me: apart from deleting Derived Data , I make an SVN update or revert any file of the project. If the project file itself is changed my Xcode displays wrong target ,so I close the project and re-open it and then indexing starts properly.
The most reliable way I've found to force re-indexing of the project is to change the build settings, specifically 'Run Static Analyzer' - I wish I had a real answer though.
This might seem like a silly response, but have you tried to repair file permissions under disk maintenance?
Your thread is old, but anyway...
Deleting the derived data folder helps me everytime. I have to do it quite regularly, which is very annoying. Your find the path in the xCode-Settings(cmd+,) in the locations-tab.
I just had this issue. What worked for me is clearing the derived data, then closing the project and re-opening it. It didn't reindex until I closed and re-opened the project. The project never compiled fully, so it didn't even have to finish building to work.