Error building after installing via CocoaPods — Include of non-modular header inside framework module 'Mapbox'

[lucacorti]

Hello,

I am not able to use the Cocoapods pckages framework with Xcode 7.2 and Swift. When building the application I get:

Pods/Mapbox-iOS-SDK/Mapbox.framework/Headers/Mapbox.h:16:9: Include of non-modular header inside framework module 'Mapbox'

[1ec5]

Pretty sure this is CocoaPods/CocoaPods#4420, which is fixed in CocoaPods master. It’s tripping up because we now include a module map that’s redundant with the one CocoaPods creates for us.

/cc @incanus

[lucacorti]

Is there any workaround to make it work right now? The Pod is unusable in its current state and the Cocoapods fix is not released yet.

[lucacorti]

I tried importing the header in the the Objective-C bridging header. Stile gettoni the dame error though.

Il giorno 16 dic 2015, alle ore 05:41, Roman Simenok notifications@github.com ha scritto:

I also have issue with mapbox imports, fix it by #import <Mapbox/Mapbox.h>

—
Reply to this email directly or view it on GitHub.

[1ec5]

I haven’t tried it out yet, but as several commenters in CocoaPods/CocoaPods#4420 point out, you should be able to use something like this to “fix” the Mapbox iOS SDK headers for now:

post_install do |installer|
    `find Pods -regex 'Pods/Mapbox-iOS-SDK/.*\\.h' -print0 | xargs -0 sed -i '' 's/\\(<\\)Mapbox\\/\\(.*\\)\\(>\\)/\\"\\2\\"/'`
end

/cc @friedbunny

[friedbunny]

That post_install bit does appear to work, got around the Include of non-modular header inside framework module 'Mapbox' build error.

[1ec5]

Fixed in #3183. If you still run into this error, make sure your bridging header isn’t importing an individual header but rather the umbrella header (Mapbox/Mapbox.h) or module (Mapbox).

[1ec5]

Actually, I still get this error in at least one CocoaPods project written in Swift after upgrading to 3.1.0-pre.1 (which is out now, by the way!). The workaround is to add #import <Mapbox/Mapbox.h> to a bridging header. You may need to clear your module cache before rebuilding.

[1ec5]

v3.1.0-pre.2 (podspec) is out with the fix for this issue. Please let us know if you still see the errors. Thanks!