title: Old libraries, new CocoaPods
body: <p>Because <strong>CocoaPods 0.36</strong> are availbable to anyone and they are now coming with Swift and Frameworks support I have one question that is bothering me today...</p>
  
  <p>I create <code>Podfile</code> in my project directory, fill it with:</p>
  
  <pre><code>source 'https://github.com/CocoaPods/Specs.git'
  platform :ios, '8.0'
  
  pod 'AFNetworking'
  pod 'SwiftyJSON'
  </code></pre>
  
  <p>And run <code>pod install</code> as usual... You know this story. But when I open my <code>.xcworkspace</code> and go to any ViewController and <code>import SwiftyJSON</code> it just works but when I try to do the same thing with AFNetworking I get <code>No such module 'AFNetworking'</code>. Of course, I can create a <strong>Bridging-Header</strong> and import it with the Objective-C way but when I read <a href="http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/" rel="nofollow">this</a> blog post I can see:</p>
  
  <blockquote>
    <p>To use this subspec in Swift, without a generated umbrella header, you
    would need to create a bridging header and use an import like <code>#import
    &lt;AFNetworking/AFNetworking+UIKit.h</code>. With the generated umbrella
    header, you just need to <code>import AFNetworking</code>, if you have the subspec
    included in your Podfile.</p>
  </blockquote>
  
  <p>Correct me if I'm wrong but I suppose that manual Bridging-Header is no longer needed if we add libraries with CocoaPods, right? So, why this isn't working?</p>