Reputation: 1871
I just discovered that I had a number of warnings in a dynamic framework (swift) that were never appearing in my issue navigator because my main project was selected for building. Is this normal? Is there a way to tell Xcode to always display warnings for child frameworks as well? I don't want to ever accidentally miss warnings like this again simply because I'm building everything.
To be clear, this has nothing to do with the issue filter not being blank.
Upvotes: 0
Views: 783
Reputation: 969
Edit the scheme for your app. Go to "Build"->Build, press the +, and add your dynamic framework(s).
When I did this, the warnings for my framework appeared immediately, and stay up-to-date just like in the code of the main app.
Upvotes: 8
Reputation: 1069
Xcode only compiles the classes of the target of your scheme.
Therefore it only shows warnings for the current target and compiling errors if it is depending on the dynamic library target.
If you want to see the warnings of other targets just like your dynamic library, try to create a new target + scheme containing all files. You don't need to use it as your main target, but once in a while you can use it to check if you have any unresolved warnings.
Alternative (pure speculations): I thought to remember that you can depend on multiple targets. Maybe you can apply this technique for your case.
Upvotes: 0