-
-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Pods failing for swift3.0 #1602
Comments
Use master. It is swift 3.0 compatible. But it is charts 3.0. We don't have plans to support 3.0 for 2.2.5 |
Ok, I just changed it to downloading from the master brach. Unfortunately, it's the same problem. I open my .xcworkspace file and Xcode wants me to convert charts into swift3. If I refuse, it then spawns over 2000 compiler errors... |
And I'm not seeing any errors from the pod update either: MacBook-Pro:Disease raw996$ pod update CocoaPods 1.1.0.rc.2 is available. For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.1.0.rc.2 Analyzing dependencies |
Is "use legacy swift" set to yes in your project? |
if all else fails. Set "use legacy swift" to false, delete our pods directory and run |
Ok, I just created a new project from scratch and repeated all of the above stuff, and it worked :-) So I now have an empty project with charts, so I will copy all of my old code into the new project. It must be something stupid with Xcode, where it refuses to let go of the old compiler errors. Thanks for the help! |
Hi,
I tried adding this line to my pod file to install the swift 3.0 version:
pod 'Charts', :git => 'https://github.com/danielgindi/Charts.git', :branch => 'Chart2.2.5-Swift3.0'
It installs properly, but the downloaded version doesn't seem to be swift3, as Xcode gives me over 2000 error messages for Charts...
Any ideas as to how I can get the beta/unstable swift3 charts version into my Xcode project via pod files?
Thanks!
The text was updated successfully, but these errors were encountered: