This is a bug in Cocoapods -And probably it won’t be fixed in a long while- Running export COCOAPODS_DISABLE_DETERMINISTIC_UUIDS=YES on the Terminal seems to suppress the warnings for now. EDIT Feb 2016: In latest version of Cocoapods this has now been moved to the install section of the Podfile: install! ‘cocoapods’, :deterministic_uuids => false
Go to your project -> Targets -> Build Phases -> Link Binary with Libraries. Then change the library you want to weak-link from “Required” to “Optional”.
From this Apple Developers Forum discussion, user dshirley and bwilson suggest using command line tools otool and grep to check if bitcode sections exist. $ otool -l libName.o | grep __LLVM or $ otool -l MyFramework.framework/Versions/A/MyFramework | grep __LLVM Running the above command, if the library contains bitcode you will see segname __LLVM output.
found it! i have copied the SystemConfiguration.framework into my project folder (checking the box when i added from xcode). deleting that folder in my project now compiles well
If you’re targeting iOS versions less than 6.0, you’ll need to make AdSupport.framework, Social.framework, and Accounts.framework optionally-linked. Please have a look at the attached screenshot. Cheers!!!
This has fixed it for me: Open up the workspace. Click on the blue project icon (that expands into your file tree) on the left hand side of the screen Just to the right, select “Targets” (as opposed to “Project”–Project is blue, Target is like a pencil and a ruler and a paintbrush making a … Read more
More of a comment than an answer, but I don’t have enough reputation for it: Have you tried using the cocoapods xcode plugin? I use it and it structures the pods on its own, so I don’t even have to worry about it.
My solution was to take the source code from the cocoa pod and create a Cocoa Touch Framework for it. Then I linked the framework to my api and to my test app. This isn’t great but it is all I could do quickly. I believe Cocoapods is working on supporting frameworks so this solution … Read more
In your Podfile, you specified use_frameworks!. As a result, the Objective-C code you’re including as a dependency (DBSphereTagCloud) is packaged as a framework, instead of a static library. Please see CocoaPods 0.36 – Framework and Swift Support for more details. As a consequence, you don’t need a bridging header file. It’s enough for you to … Read more
For your watch/today-widget extension target (so not your app or libray target), go into the project settings and change the build setting APPLICATION_EXTENSION_API_ONLY / Require Only App-Extension-Safe API to NO.