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
cocoapods 1.0.0 crash #71
Comments
I couldn't replicate this. |
I'm getting this too. For what it's worth I'm getting this on a project which was previously using CocoaPods 0.39 or whatever the last non-beta one before 1.0 was, then when I upgrade to 1.0 I get this issue. Happens on FontAwesome.swift 0.7.1 and 0.7.3. |
@DKalachniuk @CAPIStkidd I could not replicate this. Can you send in a sample project that replicates this crash? |
I can't send the main project I was working with for obvious reasons, but I just created a gutted version of it to recreate the issue to send... except the issue doesn't show up in the gutted version. I'll see if I can diff the two and figure out anything good but yeah, this is weird. |
@CAPIStkidd So there might be something wrong with your project's settings, not with this library. If you could make the gutted version crash, I'd be happy to help. You might want to try removing this from your Podfile, |
And now my main project doesn't have the issue anymore either (as in, after doing an upgrade with CocoaPods 1.0 it no longer has the crash where it can't find the otf/bundle). One thing to note is that I wasn't on board with the changes to the podfile syntax (everything has to be in a target) so I did that, maybe that had something to do with it. |
Correct! From CocoaPods 1.0,
|
I have set the target then also I am getting the same issue! |
Hi, since I updated to cocopods 1.0.0
I receive this crash
Please advice
this is my podfile
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
use_frameworks!
target 'MyApp' do
pod 'ECSlidingViewController', '
> 2.0.3'> 2.5'pod 'AFNetworking', '
pod 'PNChart', '~> 0.7.1'
pod 'FontAwesome.swift'
end
The text was updated successfully, but these errors were encountered: