Re: Indexing broken for one project

2022-02-13 Thread Alex Zavatone via Cocoa-dev
This seems to indicate an error somewhere in the Xcode prefs. Try using it in that new user is aways am option. Or copy the project back into another folder and see if the original user can open the project from the other folder. Just the two guesses I have at the moment. Cheers, Alex

Re: Indexing broken for one project

2022-02-13 Thread Gabriel Zachmann via Cocoa-dev
This is, indeed, strange. I tried it, as you suggested, with a new user account on the very same machine. Everything works just fine in a copy of the project under that pristine account. Even when I launch the .xcodeproject in my real home, the indexing works. It just does not work in my home.

Re: Indexing broken for one project

2022-02-13 Thread Ben Kennedy via Cocoa-dev
On 13 Feb 2022, at 1:07 pm, Gabriel Zachmann via Cocoa-dev wrote: > Just now, I have tried a few other things. > I deleted some folders in ~/Library/Deverlopers (caches, log files, devices). > Interestingly, there is no ~/Library/Deverloper/Xcode/DerivedData! (which > should contain the

Re: Indexing broken for one project

2022-02-13 Thread Gabriel Zachmann via Cocoa-dev
> > Sort of straw-grasping I would try with Xcode under these circumstances? > > Try changing the target CPU/OS setting to something else, build, and see if > the indexing works. > > If it does, make the minimal changes needed to appropriately build your > target. > Thanks a lot for the straw ,

Re: Indexing broken for one project

2022-02-13 Thread Gabriel Zachmann via Cocoa-dev
> This seems to indicate an error somewhere in the Xcode prefs. Oh, wow, maybe I have resolved the issue! The Derived Data directory is set to /tmp (i have had that setting for years). Now, in Xcode / Preferences / Locations / Derived Data / Advanced, I set Custom = Relative to Derived Data.

Re: Indexing broken for one project

2022-02-13 Thread Marco S Hyman via Cocoa-dev
On Feb 13, 2022, at 4:39 PM, Jack Brindle via Cocoa-dev wrote: > > In Monterey, /tmp is now only writeable by root. ??? Does terminal.app have special privs? ~% ls -l /tmp lrwxr-xr-x@ 1 root wheel 11 Feb 6 13:22 /tmp@ -> private/tmp ~% ls -ld /private/tmp drwxrwxrwt 23 root wheel 736

Re: Indexing broken for one project

2022-02-13 Thread Jack Brindle via Cocoa-dev
In Monterey, /tmp is now only writeable by root. It is quite possible that Xcode couldn’t write there for the indexing. When you changed to a new account, it probably changed where the derived data went. It used to be that /tmp was writeable by anyone. That change bit me recently as well.

Re: Indexing broken for one project

2022-02-13 Thread Alex Zavatone via Cocoa-dev
> On Feb 13, 2022, at 4:09 PM, Gabriel Zachmann wrote: > > The Derived Data directory is set to /tmp (i have had that setting for years). Oh, don’t do that. Glad you’ve got it fixed. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please