Open Radar

 
Summary:
A search scope that includes system frameworks will not actually search or match against any of the frameworks that are linked to by the targets in a workspace. It appears that it will only search frameworks that are explicitly included as file references in the project navigator.

This makes some sense, and has a long history e.g. with the old "Other Frameworks" group that was included in projects by default, in additino to the "Linked Frameworks" group. 

But the approach is needlessly confusing and particularly out of alignment with Apple's modern project templates, which tend to favor implicit library dependencies, and do not include any system frameworks whatsoever among the project's references.

It's valuable and useful to "Search against all the frameworks my targest link against" and is probably the behavior that most people would expect when selecting this search scope. The fact that Xcode knows enough to implicitly (and/or explicitly) link the required frameworks, means it should also know enough to include all of those frameworks in the search scope.

Steps to Reproduce:
1. Create a new Cocoa Application using default Xcode project template.
2. Build and run to confirm that Cocoa has been linked to by the project.
3. Click the magnifying glass to activate the search navigator.
4. From Search Scopes select "Workspace & Frameworks"
5. Search for something guaranteed to be present in Cocoa's framework headers, like "NSTextField".


Expected Results:
Matches in the linked frameworks should be included in the search results.

Actual Results:
No matches found.

Version:
Version 6.3 (6D520o)

Notes:
A related problem is that even if a framework is explcitly linked to, such as Cocoa.framework, only the header files of that specific framework will be searched, not the header files of subsidiary frameworks (e.g. Foundation and AppKit).


Configuration:


Attachments: