After update to Release 3, I can't do a build unless I delete the previous build - get file system error #105.
at the office we have seen with our clients a lot of odd little bugs with 10.13 both 10.13.0 and 10.13.1. To the point they are starting to restrict their developers to not use the 10.13 betas except for a 100% (spare) test machine. not even for their developer’s laptop.
all the people I support run 10.12 or below. Except one fool that “has to have” 10.13, none of them run it. that one person has issues all the freakin time. I don’t think 10.13 is ready for prime time.
I ran across the #105 error recently myself, using 2017 R2.1 on macOS 10.12.6.
I wasn't able to reproduce it reliably, so I didn't file a Feedback report. But after my little fix, it went away (including the temp folder).
I hope that helps. Good luck.
Edited: typo on the error number.
I have found that if I delete the Build file before entering a project (with the exception of one project), I can build multiple times with no error and subsequent opening of these projects (without deleting the Build file) also build with no error. There is one project that I have to delete the existing build before I can build without error and then subsequent Build attempts all have the Build error. There must be something about this project that produces the error but I can’t find what it is. if I find the problem I will post it here.
Greg, I think you have hit on something here. If I delete the icon for the troublesome app, I can build successfully without having to delete the previous build file. The question now is how do I build apps with an icon? Thanks so much for this info, I was trying many things without success until your suggestion.
Greg, I am sorry I missed your earlier post about the icon problem. Also, I updated my Mac to 10.13.2 this morning and it did not solve the build problem. I don't see others complaining about the icon problem - does this mean that it is something unique to my Mac.
Beatrix, I did not do any builds for quite some time so I just noticed the problem after the Release 3 update.
when you see this occur run
lsof +D <drag the troublesome debug build into terminal so you get the right path>
I'm VERY curious about the output as we do a very low level unlink to remove these files
Unlink is what RM calls to remove files
That they persist is VERY surprising
I've seen Quicklook and LaunchServices holding onto fileslong enough that we do not successfully remove the entire debug build