Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using cocoa pod with swift generates error:include of non-modular header inside framework module 'Bugsnag.BugsnagSink' #98

Closed
abuobaida opened this issue Feb 17, 2016 · 3 comments · Fixed by #99

Comments

@abuobaida
Copy link

<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "~/Pods/Target Support Files/Bugsnag/Bugsnag-umbrella.h"
        ^
/Users/new/Desktop/cashier/Pods/Target Support Files/Bugsnag/Bugsnag-umbrella.h:11:9: note: in file included from ~/Pods/Target Support Files/Bugsnag/Bugsnag-umbrella.h:11:
#import "BugsnagSink.h"
        ^
~//Pods/Bugsnag/Source/BugsnagSink.h:28:9: error: include of non-modular header inside framework module 'Bugsnag.BugsnagSink'
#import <KSCrash/KSCrash.h>
        ^
~//Source/Bugsnag.swift:2:8: error: could not build Objective-C module 'Bugsnag'
import Bugsnag
@kattrali
Copy link
Contributor

Thank you for the report, @abuobaida. Could you post your Podfile (and possibly Podfile.lock) so we know you are using the latest version (5.0.0)?

There is also an example project here which is integrated with Bugsnag 5.0.0 via CocoaPods, has "Allow Non-modular Includes in Framework Modules" set to "No", and does not appear to have this issue.

@kattrali kattrali added the awaiting feedback Awaiting a response from a customer. Will be automatically closed after approximately 2 weeks. label Feb 17, 2016
@abuobaida
Copy link
Author

Thanks @kattrali for your response. The issue appeared when Bugsnag is included as a dependency in another pod. It appeared after updating to Bugsnag 5.0.0. This is a sample project that has the issue here.

@kattrali
Copy link
Contributor

Thank you, the example project was perfect for figuring out what was going on. Fixing via #99.

@kattrali kattrali removed the awaiting feedback Awaiting a response from a customer. Will be automatically closed after approximately 2 weeks. label Feb 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants