I migrated my Mac to another Mac and after doing so I changed the user directory name. This has already caused many issues in other applications but I haven't been able to solve the code issue.
The problem:
Every time I open a new instance of vscode it opens with no installed extensions at all despite having installed many.
I am not very familiar with Mac yet and I have tried removing the App and redownloading as well as deleting some files from the ~/Library folder (cookies, preferences).
I have found the issue on Github with a workaround at the bottom of the issue:
https://github.com/microsoft/vscode/issues/168579
Basically, every new extension installed correctly but in the extensions.json file the path was wrong. It was looking for the extension in the wrong user directory (the old one before migrating).
I've seen a few other SO questions that are related to this; but I've been through all of the fixes with no joy.
My company had one Mac for use for the team. This worked absolutely fine. We really needed another so we have another. I exported the developer profile from the first Mac on to the second Mac. This seemed to work fine, we can test on local devices, etc. However, now we cannot upload on to the App Store from either Mac- they just get stuck on authentication with no error.
Things I've done:
Tried a different connection
Set the HTTPS proxy port to 80
Run the application loader and XCode at the same time
Regenerate our certificates and provisioning profiles
Set the build settings to various combinations of certificates and profiles
Turn it off and on again (more than once)
Update Java
Bump version and build numbers
Checked the licence agreement (no updates)
Deleted the XCode DerivedData caches
I can access the Apple developer sites just fine- developer.apple.com, the iTunes Connect stuff, all of that without trouble.
Some answers on StackOverflow suggested that we wait for some more time and be patient, others stated that restarting OR reinstalling Xcode should do the trick, but none worked for me. However, updating iTMSTransporter (Apple's command-line tool) worked for me, and if none of the above worked for you, I believe this one should ...
Simply create a back-up for the existing installation / folders, This is important because during the (new) install your previous installations will be removed by Transporter:
cd ~
mv .itmstransporter/ .old_itmstransporter/
Now run the following command to update Transporter:
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
Hope this helps somebody.
I solved this problem by erasing the private data using the builtin tool (Window -> Projects) and then deleting XCode itself and reinstalling.
Had the same problem, after update to xCode 7.0.1.
In my case, cleaning project DerivedData and reboot Mac OS fixed it.
Hi my Xcode project at some point yesterday started failing to build with the error:
Compilation failed for data model at path
'/Users/cooldocman/Library/Developer/Xcode/DerivedData/cooldocs-ejjarvdamwdcbbcpahhnbweztrmh/Build/Products/Debug-iphonesimulator/cooldocs.app/cooldocs.momd/cooldocs.mom'
I did research on StackOverflow and other sites - and none of the suggested fixes to similar sounding issues have worked for me. The issue appears to be at the intersection of SVN, Xcode, Core Data and XCUserState, and I have tried a number of steps from info I found on StackOverflow and other sites, but still have not solved this.
Here's what I have tried so far:
One stackoverflow article recommended to clean out the SImulator applications folder:
So I removed apps from under /Users/cooldocman/Library/Application Support/iPhone Simulator/5.1/Applications
... the error persisted ...
Another stackoverflow thread advised to remove the temp DerivedData folder.
So I removed all folders under
/Users/cooldocman/Library/Developer/Xcode/DerivedData
(the folders in the error message i.e. /Users/cooldocman/Library/Developer/Xcode/DerivedData/cooldocs-ejjarvdamwdcbbcpahhnbweztrmhwere
therefore were deleted)
Another article said to remove the contents of the Archives folder ...
/Users/cooldocman/Library/Developer/Xcode/Archives
Still no luck even after steps 2 and 3
Even after all the cleanup, I still see when I grep contents of my project that a reference still exists to the old "cooldocs-ejjarvdamwdcbbcpahhnbweztrmh" folder...
$ grep ejjarvdamwdcbbcpahhn //*///*
Binary file trunk/cooldocs.xcodeproj/project.xcworkspace/xcuserdata/cooldocman.xcuserdatad/UserInterfaceState.xcuserstate matches
Now how do I clean this up?
PERHAPS THE SECRET I NEED IS HOW TO CLEAN UP THIS LEFTOVER xcuserdata and hopefully that will resolve the issue - or otherwise, to use a treasure hunt analogy, it may at least open the door to another mysterious tunnel that needs to be crawled down! (and when I come out of that final cave is when I can start the actual work on what I really need to do!)
Thanks for reading and appreciate any help and insights from this group!
:-)
Regarding to xcuserdatad folder, Why not just close your Xcode and delete it in Finder or Terminal? It's safe to do that. Next time you open the project with Xcode, It will recreate it for you .
I had this same issue and none of the suggestions worked. I finally deleted the entire directory which had my project and cloned it again from Github and it fixed the issue. It's possible that some file that was git ignored wasn't getting reverted, but I didn't have time to find out which file it was.
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
I suddenly can't save any files in any of my Xcode projects in my home directory. Not sure what caused this. Here's the error I'm receiving:
I don't think Xcode is correct, since I am the owner of -- and have read+write permissions on -- the affected files.
A few other fun facts:
I can edit these files in other applications as the same user, so the problem seems to be specific to Xcode.
Other users can create and edit projects in their home directory without issue.
Running Xcode as root (via sudo /Developer/Applications/Xcode.app/Contents/MacOS/Xcode) does allow me to edit these files.
chown, chmod -R 755, etc. on the directory containing my projects doesn't help.
Disk Utility > Repair Permissions doesn't help.
Reinstalling Xcode, clearing Xcode .plists, etc. doesn't help. Failing both on Xcode 4.1 and 4.2.
Thoughts? Hopefully I'm just missing something simple.
I've just run into this issue myself. No amount of rebooting fixed it for me. In fact, it only began after a reboot. After much frustration, I used fs_usage to observer the file system calls that Xcode and any other processes were making when I attempted to save.
The results were interesting. In particular, one of the last things I saw before Xcode loaded NSAlertPanel.nib (which I assume is the UI for the error sheet), thing showed up:
revisiond.3029 getattrlist /private/var/folders/9f/_7xjwv310nb6c7yr6py_9jtc0000gn/T/TemporaryItems
Xcode.2437 mkdir /private/var/folders/9f/_7xjwv310nb6c7yr6py_9jtc0000gn/T/TemporaryItems/(A Document Being Saved By Xcode)
This looked highly suspect to me, so I investigated this directory. It turns out that
"/private/var/folders/9f/_7xjwv310nb6c7yr6py_9jtc0000gn/T/TemporaryItems" was owned by root:staff, and NOT writable by the group. Making this directory writable by the group fixed the issue for me immediately.
So, it appears this was a bad iteration between Xcode and revisiond, which is responsible for the File Coordination features in Lion. I do not know why this problem persisted for me when a reboot fixed it for others.
Check how you have this setup in source control. I've noticed with the new Xcode that if you have this under source control (svn) that that might be blocking your ability to write over the file regardless of permissions.
You may want to do an svn cleanup
from terminal issue a
ls -laE#"
There may be extended attributes or ACL (Access Control List) permissions problems. I have had that happen. It can be really bad if it has inherited attributes
If that is the case fix with
chmod -R -N
Be careful!
Looks like I had netbiosd blocked in my firewall configuration. After unblocking it and restarting my computer, the issue seems to be resolved.
I spent about two hours with this same problem. I tried all of the above. Finally, I rebooted my machine. Everything works fine after the reboot.
Everything was working fine and i ran into this issue. I tried most of the above suggestion. Finally,the MacOSX software update resolved the issue.