On Xcode 27 with macOS 27.0.1, I observed Xcode marking an existing project as locked because its file supposedly did not exist.
The project used the traditional project.pbxproj format. That file existed, parsed successfully, was readable, and had no filesystem lock flags. Command-line builds succeeded, but the editor continued to show the lock warning.
Selecting Unlock produced this error:
The file “project.xcproj” could not be unlocked. Could not find the file.
There was no project.xcproj in that PBX-format project.
A separate minimal iOS project also reproduced the same missing-file lock warning. That sample contains one application target, a minimal Swift source file, and signing disabled. This reproduction suggests the warning is not specific to the main application's source or extensions.
These observations were recorded on 10 October 2026. I have not retested the sample today.
Apple Developer Technical Support directed me to post the issue here.
Is this a known project-lock tracking issue involving the alternative project filenames? What supported diagnostic evidence would help establish why Xcode reports the project as locked, and is there a supported workaround that preserves the existing project format?
A standalone reproduction was prepared during the investigation. I can arrange to share it after checking the files for public release.
