iosfirebaseswift2cocoapodsgoogle-toolbox-for-mac

Reputation: 1213

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 :

# 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
  use_frameworks!

  # Pods for BB

  target 'BBTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'BBUITests' do
    inherit! :search_paths
    # Pods for testing
  end

end

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!

Upvotes: 90

Answers (18)

Krishna Kirana

Reputation: 478

Worked solution is

Search GoogleToolboxForMa in xcodeproj
Remove all references from the build configurations

Upvotes: 0

SLi

Reputation: 85

For those still having issues after all this. I am working on a cordova project and the issue suddenly appeared after upgrading to XCode 11.5.

Finally I was able to solve it by opening the pods.json file in the project root and remove the entry in "libraries" which belongs to "FirebaseMessaging". We were not using that and I dont know how it got there. Additionally I have changed the "Build Setting" -> "Build Active Architecture Only" to "No" everywhere.

Afterwards I opened the .xcworkspace file again and the build ran through.

Upvotes: 0

Shakeel Ahmed

Reputation: 6023

Swift 5 Simple Answer

Shift+Alt+Cmd+K  //Clean the project and Run again! 
//if not work restart Xcode and again clean it 
//Its will work happy coding

Upvotes: -1

Luiz Dias

Reputation: 1980

If you're facing the same error, in your XCode, go to:

Your Project > your target > Scroll down to Linked Framework and Libraries and check if the Library entry is dimmed:

If so, remove and add it again. In my case, I had duplicated entries and one of them was dimmed (when XCode can't find them on disk).

Upvotes: 1

bosozoku

Reputation: 77

-I search in harddrive for the GoogleToolboxForMac files, found in : /Users/Marco/Documents/iosapps/BomRetiro/Bom Retiro/Pods/Target Support Files

And then i copied the files to this folder : /Users/YourHomeFolder/Library/Developer/Xcode/DerivedData/Bom_Retiro-bsfjbazzzuwmuidqurdmjvdtnnsb/Build/Products

And then for me is resolved opening the project usinf .xcworkspace file.

Upvotes: 0

Armin

Reputation: 659

My issue was that I had a /bin/sh script that copied specific Pods which didn't exist. This was one of them. Removing the script resolved the build issue.

Upvotes: 0

Deblina Das

Reputation: 76

Go to : target -> Build Settings -> Other Linker Flags -> remove framework "GoogleToolboxforMAC" and build the project.

Upvotes: 4

Simple Maurya

Reputation: 105

I had the same issue when I tried to run it on my device. On the simulator it was working fine. I tried some of the above but it didn't work for me. I checked that I was working on .xcworkspace instead of .xcodeproj file, so I tried this one. Follow these steps to:

Open Xcode project (cocoapods project) using .xc... file.
Select Pods project in the project navigator (blue icon on left).
Under Targets, ensure Pods-ProjectName (blue icon) is selected.
Navigate to Build Settings and set the iOS Deployment Target on which iOS version you are going to run project.

Note:It is same as what you set in Project->Targets->Deployment info->Deployment Target.

Maybe someone get benefitted from this.

Upvotes: 1

Harsh K

Reputation: 77

Make sure your "Build Active Architecture settings" for both your project target and the pod are same. Setting NO in both these cases fixed my issue.

Upvotes: 0

kiran pm

Reputation: 151

its work's
1. select your project in directories
2. select General
3. Add "GoogleToolboxForMac.framework" to the Linked "frameworks and Libraries"

Upvotes: 6

Radek Stašek

Reputation: 31

Open the your-project.xcworkspace in your project destination.

1)Open terminal -> 2) $cd /project_destination -> 3) $open your-project.xcworkspace

or just open the file in finder

Upvotes: 0

Paul Beusterien

Reputation: 29572

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.

Upvotes: 15

Vinay Kumar

Reputation: 3267

Framework Not Found

When using Pods, we usually face this issue.

There are two main reasons for this

When we open the .xcodeproj file instead of .xcworkspace as mentioned by izaaz-yunus in this Answer
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

Pod Project Screenshot

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

Finally clean and rebuild your project.

Upvotes: 42

Izaaz Yunus

Reputation: 2828

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.

Upvotes: 169

Ravi Kant

Reputation: 13

    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]: https://i.sstatic.net/E7mjX.png
  [2]: https://i.sstatic.net/wCwET.png
  [3]: https://i.sstatic.net/KVGKM.png

Upvotes: -6

TomV

Reputation: 1232

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: LIBRARY_SEARCH_PATHS OTHER_LD_FLAGS GCC_PREPROCESSOR_DEFINITIONS

Upvotes: 5