FBSDKCorekit.h, FBSDKCopying.h file note found using Cocoapods

Question

For some odd reason after adding an unrelated pod I have been receiving an error message during the build process that indicates FBSDKCorekit.h, FBSDKCopying.h and FBSDKButton.h files are not found. I have followed countless suggestions changing properties in the projects build settings based on suggestions I've found on stackoverflow; however, none seem to work.

I am using Cocoapods so I attempted to uninstall and reinstall it as well as the pre-release version. I cleared the pod cache as well as removed the actual pods folder and podfile.lock and the xcworkspace and re-installed the pod into the project; however, I still recieve the error.

I also removed the project cache and rebuilt it...

Any assistance would be appreciated

Podfile

# define a global platform for your project
platform :ios, '8.4'
# using Swift
use_frameworks!
#
source 'https://github.com/CocoaPods/Specs.git'

# disable bitcode in every sub-target
post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['ENABLE_BITCODE'] = 'NO'
        end
    end
end

target 'MyApp' do
#   other pods
    pod ...
#   Facebook
    pod 'FBSDKCoreKit' , '4.9.0-beta2'//4.8 gives same issue
    pod 'FBSDKLoginKit', '4.9.0-beta2'
    pod 'FBSDKShareKit', '4.9.0-beta2'
#   Uber(New pod added)
    pod 'UberRides' //actually just realized it's just a wrapper for very simple calls

#   ==============================================================
#   Sets the inheritance mode for the tests target inheriting 
#   only the search paths   
    target 'MyAppTests' do
        inherit! :search_paths
    end
end

Answer 1

Happened with me after update to cocoapods 1.0.0.beta.6

Next helped to me:

• Xcode -> Product -> Clean
• Xcode -> Product -> ⌥ + Clean
• close Xcode
• rm -rf ~/Library/Developer/Xcode/DerivedData
• open Xcode and build (was no need to reinstall pods)

Answer 2

There seems to be some bug in cocoapods 1.0.0 Beta versions. Falling back to v0.39.0 fixes the error. You might need to remove cocoapods latest beta you have that installed, this question should help.