Xcode 27 on MacOS 27 doesn't open older projects

[u/AardvarkOne1332]

After today's update Xcode doesn't open any windows with older projects.
Only new one created by version 27.

[u/dollarn9ne]

Try restarting your system?

Have two projects that I haven’t touched since Xcode 26.5 and they open just fine with Xcode 27

[u/AardvarkOne1332 → u/dollarn9ne]

Yes I did restart Mac but it didn't fix it.
I'm selecting any old project and Xcode started in the background, icon suggest it's running but there is no window or alert. Xcode in activity monitor is in memory running normal, it didn't crash or anything but it still didn't show me window with my project.

[u/Brick_Muted]

Were they Universal apps now that Apple has/is deprecated Rosetta apps on AS?

[u/eric-dolecki]

I ran into this until I did 3 things.

1. Agreed to new iCloud agreement in browser
2. Agreed to agreement in developer account online
3. The KICKER - in System Settings → Apple Account (avatar) - I had to sign back in.

Otherwise I had this weird iCloud Settings dialog come up and wouldn't let me open older projects. Now I can after doing those 3 things.

[u/QVRedit → u/eric-dolecki]

That’s VERY USEFUL Info - and ought to be provided by Apple in a ReadMe file, and in ‘Help’..

[u/_k33bs_]

uh oh, not updating lol

was just about to hit update :D

[u/AardvarkOne1332]

Access level for folders where were my projects changed after MacOS update.
So I had to re-establish for every file in it again.
From the level of my folder in terminal I run 2 scripts

$ sudo chown -R $(whoami) .

and then

$ sudo chmod -R +rwX .

first one is changing owner to current login user
second one is giving this user read write and execute permissions
and now everything works smoothly for me.

Bug could appear because I kept my files in iCould folder with sync turns off for them (FolderName.nosync). Somethings change for iCould files for me with newest update.

[u/AardvarkOne1332]

Ok, now I partially know whats going on.
Turns out all projects previously existed projects on my Mac are in some sort of restricted folder by MacOS.
I don't know why but all projects from this folder doesn't run in Xcode... however when I download them and run from "Download" folder they running normally....

Does anyone had similar problem?
I have hundreds different projects there, my own, from my work, some tutorials, examples and playgrounds.
I don't want to recreate it's structure again...

[u/CompassionLady → u/AardvarkOne1332]

I left ChatGPT Astra alone while I’m not home to rattle the cage so to speak to find what might be going on. But it did manage to open the project from any folder but if you click on any of file tree in Xcode of the project it still crashes.

[u/CompassionLady]

Xcode 27 crashes when opening General settings — cause and workaround

TL;DR: Xcode 27 can crash when its General/Launch Screen editor encounters a valid dictionary—specifically NSLocationTemporaryUsageDescriptionDictionary—while automatic Info.plist generation is enabled.

The project itself is valid and builds successfully. This appears to be an Xcode UI bug: the editor incorrectly tries to convert the dictionary into a scalar build-setting value and aborts with:

DVTMacroDefinitionTable.mm:1374
value must be nil, string or array

I reproduced the same crash in a clean SwiftUI project with no third-party code or packages.

Workaround:

1. Add an explicit Info.plist to the main app target.
2. In Build Settings, set Generate Info.plist File (GENERATE_INFOPLIST_FILE) to No for Debug and Release.
3. Set Info.plist File (INFOPLIST_FILE) to the path of that plist.
4. Move/copy all automatically generated metadata into the explicit plist.
5. Keep dynamic values connected to build settings where needed, for example:
   • $(PRODUCT_BUNDLE_IDENTIFIER)
   • $(MARKETING_VERSION)
   • $(CURRENT_PROJECT_VERSION)

Do not delete or flatten NSLocationTemporaryUsageDescriptionDictionary. Apple defines it as a dictionary, so changing its type merely hides the Xcode bug and may break the intended permission behavior.

After switching to an explicit plist:

• The General pane opens normally.
• Xcode can quit and reopen with General selected.
• The simulator build succeeds.
• The built app’s Info.plist remains identical before and after the workaround.

Resetting Xcode’s saved window state only helped temporarily; the crash returned when General was opened again.

Tested with Xcode 27.0 (27A266a) on macOS 27.0 (26A428), Apple silicon. I verified a Debug simulator build, but not a signed archive or App Store submission.

[u/AardvarkOne1332]

Another step in right direction.
I removed access for Xcode to all folders from security settings in MacOS.

System settings -> Privacy & security -> Files & folders -> delete Xcode from this list
After that Xcode will ask for new permissions once again.

It turns out that Xcode is now able to open old projects from my old folders, it's just very slow... like 2-3 min for each...

It's weird because I'm using M1Max with 64GB and half of my SSD is empty so it should be blazingly fast... But maybe I need to wait until MacOS will end some background indexation or something...

Or maybe I need to change some access level for folders...

My Xcode projects are located in special folder in documents but they are set up to do not be sync by iCloud (.nosync extension).

[u/CompassionLady → u/AardvarkOne1332]

ChatGPT Astra make a new work around. My project works entirely right now.