title: Google Cloud Messaging Bridging Header import fails
body: <p>I'm implementing Google Cloud Messaging in my Swift iOS app. 
  I was following this guide: <a href="https://developers.google.com/cloud-messaging/ios/client?ver=swift" rel="nofollow noreferrer">https://developers.google.com/cloud-messaging/ios/client?ver=swift</a> </p>
  
  <p>First I changed the pods file, then I ran pod install. This worked fine.
  Since Swift needs a bridging header to include the ObjC Library I extended my header like suggested in the guide to</p>
  
  <pre><code>#import &lt;Google/CloudMessaging.h&gt;
  </code></pre>
  
  <p>But the import fails - file not found.</p>
  
  <p>I noticed the fact that CloudMessaging.h is not in the Google folder directly but in Google/CloudMessaging. Unfortunately the import of </p>
  
  <pre><code>#import &lt;Google/CloudMessaging/CloudMessaging.h&gt;
  </code></pre>
  
  <p>works neither.</p>
  
  <p>Here is a screenshot of what my pods look like</p>
  
  <p><a href="https://i.stack.imgur.com/1uot5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1uot5.png" alt="enter image description here"></a></p>
  
  <p>Did anyone notice the same problem? Any Ideas to fix it?
  Project builds fine except that the GCM classes are not found since the header is not found.</p>
  
  <p>Digging deeper:</p>
  
  <p>I tried to add CloudMessaging from scratch:
  I ran pod init and changed the podfile to</p>
  
  <pre><code># Uncomment this line to define a global platform for your project
  # platform :ios, '6.0'
  
  target 'Google Cloud Push iOS' do
  pod 'Google/CloudMessaging'
  end
  
  target 'Google Cloud Push iOSTests' do
  
  end
  </code></pre>
  
  <p>then it works</p>
  
  <p>If I use my podfile </p>
  
  <pre><code>source 'https://github.com/CocoaPods/Specs.git'
  #platform :ios, '8.0'
  use_frameworks!
  
  pod 'Alamofire', '~&gt; 1.3'
  pod 'ObjectMapper', '~&gt; 0.14'
  pod 'AlamofireObjectMapper', '~&gt; 0.7'
  pod 'HanekeSwift'
  pod 'Google/CloudMessaging'
  </code></pre>
  
  <p>the error remains</p>