Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Compiler Version for Xcode 8 #5521
What did you do?
What did you expect to happen?
Install all pod dependencies correctly.
What happened instead?
The pod is installed but the compiler version setting is not respected and Xcode 8 defaults for Swift 3
# Uncomment this line to define a global platform for your project platform :ios, '9.0' use_frameworks! target 'Concert Playlist' do pod 'Onboard' pod 'Localytics' pod 'BuddyBuildSDK' pod 'Doorbell' pod 'Google/Analytics' pod "LaunchKit" pod "Branch" pod 'Charts', :git => "https://github.com/opswhisperer/Charts.git", :branch => "xcode8_swift23" pod "AFNetworking" pod 'FBSDKCoreKit' pod 'FBSDKShareKit' pod 'FBSDKLoginKit' pod 'iRate' pod 'GoogleConversionTracking' pod 'UIBarButtonItem-Badge', :git => "https://github.com/mikeMTOL/UIBarButtonItem-Badge.git" pod 'GoogleIDFASupport' end
This project is using swift 2.3, if you install it, Xcode does not set the compiler version
As a work around I did this
But it really should preserve whatever is in the framework if it is set
I think we should generate the build setting with
I don't think that it is feasible to add this to the podspec as there is no clear definition on what e.g. Swift 3.0 is until the stable version ships. So there really isn't a way for CP to determine if a certain Pod would actually build with whatever Swift version is currently being used.
@neonichu I'm not sure what this means:
added a commit
Jun 26, 2016
added a commit
Sep 13, 2016
Hey guys, which version of Cocoapods do I need in order to not use this workaround - #5521 (comment)? Is it specified/documented anywhere?
I'm still getting “Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly." errors for pods.
bundle exec pod --version 1.0.1
@tomaskraina That workaround is working for me with Cocoapods 1.0.1. My Podfile: