New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflicting base configuration warnings #3112
Comments
I deleted my Podfile: workspace 'JiveKit'
xcodeproj 'JiveKitDemo/JiveKitDemo'
source 'https://github.com/CocoaPods/Specs.git'
target :JiveKitDemo do
pod 'JiveKit', :path => 'JiveKit.podspec'
end
target :JiveKitDemoTests do
pod 'JiveKit/Testing', :path => 'JiveKit.podspec'
end JiveKit.podspec: Pod::Spec.new do |s|
s.name = 'JiveKit'
s.version = '0.1.0'
s.license = { :type => 'Apache License, Version 2.0', :file => 'LICENSE' }
s.summary = 'Swift SDK for the Jive REST API.'
s.homepage = 'https://github.com/jivesoftware/JiveKit'
s.authors = { 'Jive Mobile' => 'jive-mobile@jivesoftware.com' }
s.source = { :git => 'git@git.jiveland.com:jive-kit', :tag => s.version }
s.ios.deployment_target = '8.1'
s.osx.deployment_target = '10.10'
s.requires_arc = true
s.default_subspec = 'Core'
s.subspec 'Core' do |core|
core.source_files = 'JiveKit/Source/*.swift'
core.dependency 'Alamofire'
end
s.subspec 'Testing' do |testing|
testing.source_files = 'JiveKit/Testing/*.swift'
testing.dependency 'JiveKit/Core'
end
end However, now when I try to run my tests, I get the following error in the console:
/var/folders/k9/pfhv0hgd5_b4tm8fm1xmjmx496st3c/T/com.apple.dt.XCTest-status/Session-2015-02-04_11:26:11-LUJbcy.log:
I'm guessing that there are duplicate symbols in |
@hborders Could you try both cleaning and deleting derived data before trying to run the tests. |
Odd: if you do a search for a Google search for "Error 3588 loading bundle" this is literally the only hit. I'm also experiencing this problem but it was after changing the version of a pod (CocoaLumberjack from 2.0.0-rc2 back to 1.9.2). Now I get the above error about injecting the XCTest bundle when trying to run tests on iOS 7 in the simulator. It works fine in iOS 8. Before changing the version back, it worked on all iOS simulator versions. If I git stash my changes and go back to my previous setup, things still work fine. I have tried resetting the simulator, deleting DerivedData, everything. :-( |
I discovered my issue after running on an iOS 7 device, as opposed to the simulator. It was caused by this issue related to Apple's mistake in asl.h. (see: Cocoanetics/DTFoundation#69 and related issues) Doesn't seem related in any way to what you are experiencing, but wanted to give the update. |
This is because you have pods in the implicit Pod target and explicit Pod target. The implicit target will be integrated into the same target that your explicit targets You can notice this by the warnings at the end of
To solve this problem, move the Pod in the implicit Pod target into each target instead, as follows: source 'https://github.com/CocoaPods/Specs.git'
workspace 'JiveKit'
xcodeproj 'JiveKitDemo/JiveKitDemo'
target :JiveKitDemo do
pod 'SwiftHamcrest', :path => 'Pods-ified/SwiftHamcrest'
pod 'JiveKit', :path => 'JiveKit.podspec'
end
target :JiveKitDemoTests do
pod 'SwiftHamcrest', :path => 'Pods-ified/SwiftHamcrest'
pod 'JiveKit/Testing', :path => 'JiveKit.podspec'
end Currently the Podfile syntax allows you to attempt to do this but it's not possible. CocoaPods won't let you do this when #840 is complete. |
I'm very confused here, Kyle. Basically you say that the
This is just not true then. It will not inherit them. Instead they will conflict with each other. |
@TGOS I never mentioned the |
@kylef You said that it is not possible to have pods in exclusive and inclusive targets at the same time. You said that this is not possible (= not going to work):
According to documentation it is. According to documentation a Podfile like above means that
But if only the exclusive sample above works as well as the following:
Then the exclusive flag is meaningless, because per target pod settings must always be exclusive, everything else cannot even work. That means the exclusive flag is a flag to suppress behavior that isn't even supported in the first place. |
Podfile:
JiveKit.podspec:
This causes the following output (from
pod install --verbose
):I'm running Xcode Version 6.1.1 (6A2008a). I simply created
JiveKit.xcworkspace
and addedJiveKitDemo.xcodeproj
inside it using the "Single View Application" template, then quit Xcode and ranpod install
using the files above.I tried following the instructions in the output, and I noticed that the
JiveKitDemo/Pods
Group contained no references to thePods-JiveKitDemo.debug.xcconfig
orPods-JiveKitDemo.release.xcconfig
files, so I couldn't set theJiveKitDemo
project's base configuration to them. I added the files to the group and then updated the base configuration as instructed. Then, I ranpod install
again to make sure there were no more errors, and I got the following new error:Now, I have conflicting warning messages, so I'm not sure this configuration can work at all. This definitely seems like a bug, but maybe there's a better way to handle my goal: to have cocoapods manage my demo project and the tests associated with my demo project.
The text was updated successfully, but these errors were encountered: