I'm working on an older project that's got a third party library that in turn has a few different Cocoapods that it requires. One of the Cocoapods is keeping the project from building with the aforementioned "Include of non-modular header inside framework module" errors on imports in one of the header files. The common answer to this seems to be setting "Allow Non-modular Includes In Frameowrk Modules" to Yes, but that hasn't had any affect either in the Project or Target build settings.
The part that's extra weird is that if I create a new Xcode project and add these pods, it builds no problem, as does the sample app that the people who wrote the third party library provided which also installs the pods. I've gone through every single build setting in the project that's failing and both of the newer projects that aren't failing, and checked every place that I could think of, but almost everything is identical and fiddling with the ones that aren't identical haven't had any luck. I've cleaned the project, deleted the derived data, and done a fresh pod install every step of the way, but still nothing. Creating a fresh project and re-creating everything isn't really a viable option, as it's a pretty large codebase with a lot of ties to a lot of places, so I'm trying to find a solution that isn't that.
Another thing that's worth mentioning, I can go into the file where the problematic imports are and replace the three "#import <pod/podheader.h>" lines with a single "@import pod;" line, and when I do that it'll compile and run just fine. But the deployment is automated with a server that does a fresh pod install every time, so that's not really a workable solution either, and the pod isn't super well maintained so I haven't heard anything from them. Since everything works on other projects, though, they shouldn't actually need to change anything, I'm just out of ideas as to what it could be in my project that's tripping it up.