Re: Many new warnings after Xcode upgrade
I don’t have any special insights, but I think the warning is correct in that there has for some time been an (unwritten?) rule that the #imports *inside* a framework header should use angle brackets — for self-preservation.toggle quoted messageShow quoted text
Again with no special knowledge, that makes sense to me because imports with double-quotes will search the framework *client’s* include paths first, and that’s almost certainly wrong if there are any symbol conflicts with what’s defined in the framework.
OTOH, it’s hard to predict the effect of “fixing” the bracketing, because Xcode’s behavior here is somewhat inscrutable.
All that said, my suggestion is as follows:
1. Commit your project as-is to the repository.
2. Apply all the “Double-quoted include …” warning fixits automatically.
3. Build and run the project.
If that works, don’t lose any sleep. If something blows up, discard changes and silence the warnings, and don’t lose any sleep. :)