Skip to content
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

0.38.1. Leaves swift (bridged) project with every pods' content undefined #3895

Closed
adamjack opened this issue Jul 24, 2015 · 3 comments
Closed

Comments

@adamjack
Copy link

Xcode Version 6.4 (6E35b)

Going from (I believe) 0.38 (working) to 0.38.1 (not working) I had to rename/change case of a number of the pods. Once past that I could not get the contents of the pods. Every reference would result in a "not defined" (sorry, don't have build log with errors.) It seems like nothing in the pods was available to my project. Restoring to 0.38 works.

Podfile:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
xcodeproj 'SomeSwiftProject', 'ADHOC' => :release
#use_frameworks!

target "SomeTarget" do
        pod     'FBSDKCoreKit'
        pod     'FBSDKLoginKit'
        pod     'FBSDKShareKit'
        #pod    'SWRevealViewController'
        pod     'AFNetworking'
        pod     'AFNetworkActivityLogger'
        pod     'google-plus-ios-sdk'
        pod     'GoogleAnalytics'
        #pod    'google-api-client'
        pod     'Quantcast-Measure'
        pod     'Reachability'
        pod     'Google-Mobile-Ads-SDK'
        pod     'comScore-iOS-SDK'
        pod     'Toast'
        #pod 'Fabric'
        #pod 'Crashlytics'
        pod 'Lookback', :configurations => ['Debug']
        pod 'LookbackSafe', :configurations => ['Release']
        pod 'OpenSans'
end
target "SomeTargetTests" do
        pod     'OCMock'
        pod     'Google-Mobile-Ads-SDK'
end
@samanthamjohn
Copy link

Also happening for me. Fix this please!!

@neonichu
Copy link
Member

I have a hard time understanding the actual error without a build log, but I'm thinking this will be fixed by #3898 regardless.

@segiddins
Copy link
Member

This should be fixed by 0.38.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants