Framework not found GoogleToolboxForMac

After I update my Firebase via “pod update”, I got error like this :

ld: warning: directory not found for option '-F/Users/bennysantoso/Library/Developer/Xcode/DerivedData/FCM-atfcxuircoryufazlomgwfgmvaqm/Build/Products/Debug-iphonesimulator/GoogleToolboxForMac'
ld: framework not found GoogleToolboxForMac
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Here my Podfile :

  • Xcode 8 and Swift 3 NSCalendar
  • perform segue with identifier wont work in swift 2
  • How can i create a user with info about Display Name, username & Profile pic?
  • Swift 2 – Cant get user location with CLLocationManager
  • Generate an RSA public / private key pair
  • Simplest way to implement a “Read More” button to expand a UITextView in iOS Swift 2?
  • # Uncomment this line to define a global platform for your project
    # platform :ios, '9.0'
    pod 'Firebase/Core'
    pod 'Firebase/Messaging'
    target 'BB' do
      # Comment this line if you're not using Swift and don't want to use dynamic frameworks
      # Pods for BB
      target 'BBTests' do
        inherit! :search_paths
        # Pods for testing
      target 'BBUITests' do
        inherit! :search_paths
        # Pods for testing

    Does anybody know about this error?

    I seek out relationships GoogleToolboxForMac and Firebase, but I just get a little bit of information.

    FYI, I use Swift 2.3 and Firebase 3.8.0.

    I will be grateful for any help you can provide. Thanks!

    7 Solutions Collect From Internet About “Framework not found GoogleToolboxForMac”

    I had the same error. Once you install the pods, you’ll see the following message.

    [!] Please close any current Xcode sessions and use MyApp.xcworkspace
    for this project from now on.

    I didn’t notice this for the first time and was trying to build the project using the regular xcodeproj file. After I saw this message, I opened the right project and it worked fine.

    Once you open this project you’ll notice that you have two subprojects. One would be your project, and another would be the Pods project.

    GoogleToolboxForMac is a dependency of Firebase/Messaging. Details in the podspec. When doing “pod update”, Cocoapods should set up your workspace to build and link GoogleToolboxForMac.

    It sounds like something about your workspace is in a bad state. Does Product -> Clean help? What about deleting Derived Data and the ModuleCache (Xcode -> Preferences -> Locations -> Derived Data)?

    It shouldn’t be necessary, but you could also try explicitly adding pod ‘GoogleToolboxForMac/Logger’ to your Podfile.

    In my case all integration are well-done and also did try so many time to remove and reinstall pod but did not get success.

    Finally try with below step

    Projetc->Manage Schemes -> Select check box “Pods-MyProjectName”

    And get success.

    This was fixed by adding $(inherited) in the Build Settings -> Search for LIBRARY_SEARCH_PATHS.

    This is understandable, since when updating your pod file for the latest versions of libraries which your project depends on, the debug output tells you where you need to add all the $(inherited) flags:

    Closed the project that I was trying to build after I did pod install then opened the .workspace and then everything builds perfectly.

    Framework Not Found

    When using Pods, we usually face this issue.

    There are two main reasons for this

    1. When we open the .xcodeproj file instead of .xcworkspace as mentioned by izaaz-yunus in this Answer
    2. When Build Active Architecture Only is set to Yes in Build Settings

      This applies to the projects target and also to all the targets in the pod project

    Main Project Screenshot
    Set Build Active Architecture Only to No

    Pod Project Screenshot
    enter image description here

    1. Select Build Settings (of main project, pod project both)
    2. Select each Target one by one
    3. Set Build Active Architectures to No for each target

    Finally clean and rebuild your project.

        Friends, you must be confused with the exact result, as i was. So, i feel to share the 
    screenshot that might be helpful. We all had to be careful that we need to change the flag for property **"Build Active architecture Only"** for **pod target** to **NO** And build, it would not show the linking error.
        See the attached screenshot.
        Screen Shot 1, Screen Shot 2, Screen Shot 3
        [Select Pods][1]
        [Select Targets in the pod][2]
        [Change flag to No][3]
      [1]: /images//E7mjX.png
      [2]: /images//wCwET.png
      [3]: /images//KVGKM.png