Cocoapods: could not build Objective-C module since beta.4

[muhasturk]

1.0.0.beta.3 has no problem. Problem seens alive since beta.4

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

Report

What did you do?

Tried build my iOS project

What did you expected to happen?

Build successfully

What happened instead?

/Users/muhasturk/Library/Developer/Xcode/DerivedData/Kidofun-dnpyvqmdyyathecqamzttcigtjgt/Build/Products/Debug-iphonesimulator/pop/pop.framework/Headers/POP.h:13:9: error: 'pop/POPDefines.h' file not found
#import <pop/POPDefines.h>
        ^
<unknown>:0: error: could not build Objective-C module 'pop'

Podfile

platform :ios, '8.0'
use_frameworks!

target 'BlaBla' do
    pod 'Alamofire', '~> 3.0'
    pod 'Crashlytics'
    pod 'Fabric'
    pod 'Koloda', '~> 2.0.8'
    pod 'SwiftyJSON'
end

[mrackwitz]

Have you tried to clean your build folder and re-build from scratch?

[muhasturk]

Yes I did two times. 1.0.0.3 has no problem.

[segiddins]

In that case, could you share a project we can use to debug?

[ejensen]

I'm experiencing something similar with beta 4:

error: 'RxCocoa/RxCocoa.h' file not found
#import <RxCocoa/RxCocoa.h>
        ^
<unknown>:0: error: could not build Objective-C module 'RxCocoa'

Podfile:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.1'
use_frameworks!

target 'The Target' do
    pod 'AsyncDisplayKit', :git => 'https://github.com/facebook/AsyncDisplayKit'
    pod 'Fabric'
    pod 'Crashlytics'
    pod 'RxCocoa'
end

Worked without a problem in beta 2 & 3

[matthijs2704]

Same here! I tried rebuilding, cleaning and removing derived data, but no results...

[segiddins]

Can anyone share a project?

[muhasturk]

I can't because it's commercial project.

[segiddins]

Then boil it down to something simpler that we can run. Otherwise, were less likely to investigate the issue.

[ejensen]

@segiddins https://github.com/ejensen/CocoaPodsBeta4Issue is a boiled down project that displays the issue. The 1st commit uses CP 1.0 beta 3. The 2nd commit updates to CP 1.0 beta 4, which causes the project to fail compilation.

[niklassaers]

I am seeing the same or something very similar. I have two mixed Swift/ObjC projects where one is dependent on the other. CocoaPods has always added the dependent project to the workspace even though it is already there, and lately it then complains of double references. Works good, though. But since 1.0.0.b4 it will not import modules such as Alamofire anymore. Only thing I need to do is gem update to 1.0.0.b4 (from 1.0.0.b3) and do a "pod install" and it will fail.

I am working on getting this project open sourced, so while I cannot share it openly just yet, I can share it privately with you, and I'd love to do a session together to try to find it together (I'm on GMT+1)

[segiddins]

@mrackwitz any interest in looking at this one?

[feifanzhou]

This project is just a template Swift project from Xcode with Atlas as the only dependency. It built fine on Cocoapods 0.39, but broke with 1.0.0b4 and 1.0.0b5.

Atlas-Swift-Test (no pods).zip

[mgrebenets]

I have created a repo with a demo target, which demonstrates an issue with tests targets.
https://github.com/mgrebenets/cocoapods-tests-with-transient-binary. The repo is using 1.0.0.beta5, this is also directly related to #4944.

[isair]

I'm having this issue on 1.0.0 release.

[marcmatta]

Having the same issue also on 1.0.0 release. Can someone help fix this please?

[jacobjiangwei]

Having the same issue also on 1.0.0 release. Can someone help fix this please?

[mrackwitz]

It's not yet confirmed to which extent this is an actual issue with CocoaPods. With the latest release some things got re-aligned, which might have caused in some cases that previously accidentally working podspecs don't work anymore. If you can still reproduce this issue, even after cleaning derived data, cleaning the CocoaPods cache, nuking the local Pods directory and installing again from scratch, then please report what podspec is causing issues for you, in the best case including a minimum reproduce sample project.

[Fawxy]

I had this issue, I cleared pod cache, nuked the Pods folder, redid pod install, and now i'm getting another error:

error: ....fssaygqyocsdwwejsgiszaapqvpc/Build/Products/Debug-iphoneos/Pods.framework: No such file or directory

Haven't been able to get past this. I also wasn't able to create a project that had the same issue despite using all the same pods and identical Podfile, however it was Segment_Mixpanel that it was complaining about for me.

Podspec here: https://github.com/segment-integrations/analytics-ios-integration-mixpanel/blob/master/Segment-Mixpanel.podspec

[aronspringfield]

I was experiencing this issue but have now solved it. The issue is with Derived Data which is why it can't be replicated in a new project.

To fix it, in XCode go to Window->Projects, find your project in that list (usually the top one if it's the open one). Then click the Delete button next to the Derived Data section. Rebuild should work.

[niklassaers]

So, perhaps a bit late, but what I saw in 1.0.0b4 is solved in 1.0.0. :-)

[c01dcat]

@aronspringfield Your answer solved my problem, thanks!

[laurilehmijoki]

On JetBrains App Code, I got around the problem with the following steps:

1. Run –> Clean Build Folder
2. Run –> Clean
3. Build

[stale[bot]]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem :+1:

[stpeterthe1]

I have the same problem