Regression on v1.0.0.beta.5: Generating modulemap instead of copying existing one

[samnung]

• I've read and understood the *CONTRIBUTING guidelines and have done my best effort to follow.

Report

What did you do?

Installed newer version of CocoaPods. Actually upgraded from v1.0.0.beta.4 to .beta.5.

I am using pod ZSWTaggedString in one project. And I've found that until version 1.0.beta.4 build was working fine, but after upgrading to .beta.5 Xcode can't build it anymore. Xcode is complaining about missing module "ZSWTaggedString.Private".

I've created minimalistic iOS project CocoaPodsModuleExperiment.zip to demonstrate issue.

Steps to recreate the project are very simple:

• Create some iOS project in Xcode
• Run pod init
• Add pod 'ZSWTaggedString/Swift', '~> 2.0' into Podfile
• Run pod install

From my investigation I think PR #4969 has to do something with this problem, but I am not sure. (And of course I don't want to blame @segiddins 😉). I think it is caused by setting public_headers only in default subspec and using another subspec in Podfile which has dependency on default subspec, well checkout the spec file for ZSWTaggedString.

Important note, during installation verbose mode it tells me that the module map was generated.

Interesting note, when I change Podfile to have following pods, the build works.

pod 'ZSWTaggedString', '~> 2.0'
pod 'ZSWTaggedString/Swift', '~> 2.0'

Now it is copying the modulemap from pod as it should be.

What did you expected to happen?

Xcode build success.

What happened instead?

Xcode build failed.

Podfile

platform :ios, '8.0'
use_frameworks!

target 'CocoaPodsModuleExperiment' do
  pod 'ZSWTaggedString/Swift', '~> 2.0'
end

[samnung]

nice 👍