Cocoapods 0.37.1 - when updating a subfile, the frameworks are no longer connected

Question

I struggled with this for several days, and I could use some recommendations.

The following is the contents of my original subfile:

pod 'Parse', '~> 1.7.1' pod 'ParseUI', '~> 1.1.3' pod 'ParseCrashReporting' 

Everything worked fine until the day I decided to add a few more pods. Here's what my subfile looks like:

 source 'https://github.com/CocoaPods/Specs.git' platform :ios, '8.0' use_frameworks! pod 'Parse', '~> 1.7.1' pod 'ParseUI', '~> 1.1.3' pod 'ParseCrashReporting' pod 'Alamofire', '~> 1.2' 

As you can see, I'm trying to add Alamofire. When i do

$ pod update $ pod install

Everything seems to be setting fine. However, when I open my project in Xcode and finish indexing, all the hell broke (well, not really).

It seems that Parse is no longer associated with my project, since I have 50+ line errors:

Use of undeclared type 'PFLogInViewController'

I'm not at all new to Ruby / Gemfiles or the command line, but I'm pretty new to Xcode and Cocoapods.

Any help would be greatly appreciated. Thanks.

EDIT: Below is my bridge title.

 // Objective-C Bridging File #import <Foundation/Foundation.h> #import <Parse/Parse.h> #import <ParseCrashReporting/ParseCrashReporting.h> #import <ParseUI/ParseUI.h> #import <Bolts/Bolts.h> 

EDIT:

I get the following error after executing pod install :

 Error: unable to read module map contents from 'Target Support Files/Pods-Parse/Pods-Parse.modulemap': Error Domain=NSCocoaErrorDomain Code=260 "The file "Pods-Parse.modulemap" couldn't be opened because there is no such file." UserInfo=0x7fc988cd4920 {NSFilePath=/Volumes/BigMan/Code/Swift/ProjectName/Pods/Target Support Files/Pods-Parse/Pods-Parse.modulemap, NSUnderlyingError=0x7fc98ac96850 "The operation couldn't be completed. No such file or directory"} 

Answer 1

The header title is only required if you are creating CocoaPods for a static library. After switching to frameworks, you should use import ParseUI in your source files.

Answer 2

Running pod install helped me solve this problem. Sometimes when working with a team other containers may be installed.

Answer 3

1) After deleting the pod files, I tried pod install again.

2) I still got the error.

3) tried pod install again.

4) Then I did pod repo update

And it worked.