XCode 7.1 : No longer builds against a development pod

[solomon23]

If you create a development pod and reference AWSKinesis and AWSCore, the project will no longer build as of XCode 7.1. It previously built clean in 7.0.1. Here's a sample project:

https://www.dropbox.com/s/98h743arecqtwrs/BadPod%202.zip?dl=0

The discussion over on cocoapods:

CocoaPods/CocoaPods#4420

[mikecole20]

+1

I'm having the same issue with AWSCore and AWSS3. My SDK (my private cocoapod) depends on AWSCore and AWSS3 and compiles fine. My app depends on my SDK (which includes AWSCore and AWSS3 in the podspec). AWSS3 gives the include of non-modular header inside framework module error when trying to compile the app. Everything worked well in Xcode 7.0.1.

[yosuke-matsuda]

We will look into this. Thanks.

[earulraj]

Any update to this issue.. Facing the same :(

[abeeriqbal]

Try to clean and rebuild your project

[rkawajiri]

Is this problem solved?

According to this PR #272, this seems to be solved. However, I'm having the same issue on my private pod with 2.3.2.

[mikecole20]

It's still a problem for me as well.

[mikecole20]

I wanted to follow up on this. We just updated our SDK to use AWSCore 2.3.2 and AWSS3 2.3.2. Still getting the same issue when importing our SDK into our App.

From AWSBolts.h:

Include of non-modular header inside framework module 'AWSCore.AWEBolts'

There are 8 of those: one for each import. This of course causes another build error in our swift file where we try to use import AWSCore.

Could not build Objective-C module 'AWSCore'

There is a workaround that I found in the previously linked Cocoapods issue.

post_install do |installer|
    `rm -rf Pods/Headers/Private`
    `find Pods -regex 'Pods\/.*\.modulemap' -print0 | xargs -0 sed -i '' 's/private header.*//'`
end

This hasn't seemed to cause any side effects for us, but I'd love to get rid of it. The Cocoapods issue was closed and stated to be fixed, but I'm still needing that workaround to get AWS working.

[yosuke-matsuda]

This issue has not been addressed. #272 is a separate issue.

[Kumuluzz]

@yosuke-matsuda, are there any updates or progress made on this issue?

[moa7ed]

Any updates??

[yosuke-matsuda]

With CocoaPods 1.0.0, this issue should have been resolved. Please let us know if you keep encountering the issue. Thanks.