Please Add the Host Targets for the Embedded Targets to the Podfile

Cocoapods 1.3.1 + XPC Service

As mentioned here: https://github.com/CocoaPods/CocoaPods/issues/6256, you need to specify your XPC service as a target dependency in your primary project.

Unable to find a target named `ProjectName`

After spending hours on Google just opened Podfile and found that project name is wrong. So I have just written correct project name in Podfile and issue has been resolved.

Before:

target 'Wrong Project Name' do
pod 'Parse'
pod 'SDWebImage'
end

After:

target 'Correct Project Name' do
pod 'Parse'
pod 'SDWebImage'
end

Using Cocoapods in an app extension using a framework

So, what gives :

  • My concern of "separating pods between targets" is absurd because you can still import them anywhere.
  • The "you have to manually link" issue is fixed by an easy import RealmSwift statement.

The fixed and working Podfile therefore is :

platform :ios, '8.0'
use_frameworks!

target 'MyApp' do
pod 'Eureka', '~> 2.0.0-beta'
pod 'PKHUD', '~> 4.0'
pod '1PasswordExtension', '~> 1.8'
end

target 'MyAppKit' do
pod 'Fuzi', '~> 1.0'
pod 'RealmSwift', '~> 2.0'
pod 'Alamofire', '~> 4.0'
pod 'KeychainAccess', '~> 3.0'
pod 'Result', '~> 3.0'

target 'MyAppWidget' do
inherit! :search_paths
end
end

And that's it. I would say that the old behaviour was more obvious and didn't require reading up on "podfile target inheritance". I did learn a lot though. Cheers!

Error on pod install --verbose

Okay!

Looks like the solution in your case was to move use_frameworks! up and out of a specific target and make it global for the Podfile.

The issues you're now seeing (in your Update 2) is that you need to go into your Project Settings and fix the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES setting. I'd recommend simply removing the build setting.



Related Topics



Leave a reply



Submit