Cocoapods: Generated Framework Search Path No Longer Valid in Xcode 7.2

Created on 10 Dec 2015  Â·  13Comments  Â·  Source: CocoaPods/CocoaPods

When building the example project of a newly-initialized pod lib, there is a warning for a missing Framework search path when building with Xcode 7.2:

(cocoapods version: 0.39.0)
pod lib create ReproduceIssue

language: Swift
Include demo: No
Include testing: None
View based testing: No

Select "ReproduceIssue-Example" target and an iPhone simulator.
Build.
The following warning should appear:

"ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/Developer/Library/Frameworks'"

The correct framework path is also included in the build command:
"-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks"

So, this warning is just an unnecessary build option.

awaiting input

Most helpful comment

Any update on this? Still an issue a year later.

All 13 comments

I believe this has been fixed on master?

I didn't see anything similar in the closed issues list. I've tried running Cocoapods from master with:

git clone https://github.com/CocoaPods/CocoaPods.git
cd CocoaPods
bundle install
bundle exec pod lib create
etc...

The resulting project from that process still had this issue.

Ok we'll look into it, thanks!

lol, I think they changed it back in Xcode 7.2 — the path we removed in c128c5a4d7af91e88a40fd714563ecf10af6ec17 exists again, but the other one has been removed 😢

Any updates on this?

This is still a valid issue, so I'm going to keep it open.

Any update on this? Still an issue a year later.

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

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:

This is still an issue!

This is a 3 year old issue. Can you please file a new one and include a sample app?

@jlubeck thank you!

Was this page helpful?
0 / 5 - 0 ratings