Open Radar

 
Summary:
When an Xcode workspace's selected scheme is associated with a project that is included as a reference in the workspace (i.e. it's not the main project in a project-based workspace), any change at all to the associated project will cause Xcode to reset the selected scheme to something other than what the user had selected.

This is particularly noticeable when working with version control because changes to a project may have occurred outside the scope of Xcode. For example when bisecting to determine the source of a problem, the project file may change with every bisect, causing a frustrating, repeated reset of the active scheme which must then be manually reset.

Steps to Reproduce:
1. Open attached SelectedSchemeTest.xcodeproj
2. Ensure the scheme "OtherProject" is selected in the Active Scheme indicator.
3. From the Terminal, simulate a change to the project file by e.g.:

touch OtherProject/OtherProject.xcodeproj/project.pbxproj

4. Switch back to Xcode and wait for it to reckon the changed project file.


Expected Results:
Unless changes to a project have caused the active scheme's target to disappear, the active scheme should remain preserved across reloads of the project.

Actual Results:
The active scheme resets to a scheme that is associated with a project that was not modfiied.


Version:
Version 7.0 beta 3 (7A152u)

Notes:


Configuration:


Attachments:
'SelectedSchemeTest.zip' was successfully uploaded.