Framework not found GoogleToolboxForMac

Question

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!

Same for me.. anybody can help? I've been all the day working on this :/ I notice that using older versions of the same library are not using GoogleToolboxForMac and works perfectly :( — Santi Iglesias, Nov 23 '16 at 13:04
From other stackoverflow answers I have tried adding all the following to my pod file but still not working: pod 'Google/Analytics' pod 'Firebase/Core' pod 'Firebase/AdMob' # Trying to fix GoogleToolboxForMac missing error pod 'Firebase/Messaging' pod 'GoogleToolboxForMac/Logger' pod 'GoogleToolboxForMac', '~> 2.1' — Charlie S, Dec 04 '16 at 19:35
First of all, format of your Podfile is old (Q4/2016). Remove it and create new one using 'pod init'. Use the workspace not xcodeproj as suggested below. — igraczech, Feb 22 '17 at 10:51

score 169 · Accepted Answer · edited Aug 10 '17 at 05:43

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.

score 42 · Answer 2 · answered Sep 22 '17 at 06:42

42

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.

answered Sep 22 '17 at 06:42

Vinay Kumar

3,257
1
20
19

is there is a typo, at #2 you saying "yes" but at image shows "no", thanks @Vinay Kumar – greenridinghood Jun 28 '19 at 19:56
#2 tells what is causing the issue and the image is how the settings should look like for the issue to be resolved – Vinay Kumar Jun 29 '19 at 13:18
All others solution doesn't work for me exept : set Build Active Architecture Only to NO for all pod library – tamtoum1987 Jan 05 '20 at 13:58

score 18 · Answer 3 · answered Dec 19 '16 at 11:19

18

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.

answered Dec 19 '16 at 11:19

iPatel

46,010
16
115
137

I got this error when running in the simulator, but didn't get it on an actual device. – mpwhitt Jan 27 '17 at 12:22
This worked for me but I had to build the pods project explicitly too before attempting to build my project. No idea why. – ApeOnFire Oct 12 '17 at 19:55
1

I did this but I can't run the app on my simulator? – Drailan John Terrible Jan 22 '18 at 03:59
2

After building the "Pods-ProjectName" I was able to run the real project on my device.. – Tim Baas Feb 21 '18 at 15:09

Paul Beusterien · Answer 4 · 2017-10-31T14:36:40.470

15

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.

edited Oct 31 '17 at 14:36

answered Nov 01 '16 at 15:47

Paul Beusterien

27,542
6
83
139

Nope this didn't worked for me...by opening project from workspace worked! – Jayprakash Dubey Mar 29 '17 at 12:08
2

@JayprakashDubey This answer assumes you're starting from the workspace. See the first paragraph. The answer solves another scenario that leads to the same symptom. – Paul Beusterien Mar 29 '17 at 16:31
1

@PaulBeusterien I tried everything you said here, but still, I can't build. – Drailan John Terrible Jan 22 '18 at 04:14

score 6 · Answer 5 · answered Nov 17 '17 at 04:31

6

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

answered Nov 17 '17 at 04:31

kiran pm

151
3
3

1

Linking the library explicitly solved it for me. Thanx! – Liquinaut Nov 30 '17 at 12:55

score 5 · Answer 6 · answered Feb 21 '17 at 15:05

5

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

answered Feb 21 '17 at 15:05

TomV

1,157
1
13
25

where to put the $(inherited) should I press + then type $(inherited)? – Drailan John Terrible Jan 22 '18 at 03:51
Yes, you can press + and input $(inherited) or simply double click on the editable box and then you can input $(inherited) – TomV Jan 22 '18 at 10:11
This fixed my problem! Thank you @TomV – Spettacolo83 Jul 06 '19 at 22:30

score 3 · Answer 7 · edited Aug 21 '18 at 14:18

3

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

edited Aug 21 '18 at 14:18

Haroldo Gondim

7,725
9
43
62

answered Aug 21 '18 at 07:08

Deblina Das

66
4

score 1 · Answer 8 · edited Mar 13 '18 at 10:24

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.

score 1 · Answer 9 · answered Nov 09 '18 at 10:53

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).

score 0 · Answer 10 · answered Dec 20 '16 at 13:53

0

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

answered Dec 20 '16 at 13:53

Satheesh

10,998
6
50
93

score 0 · Answer 11 · answered Nov 05 '17 at 19:32

0

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

answered Nov 05 '17 at 19:32

Radek Stašek

31
6

score 0 · Answer 12 · answered Mar 06 '18 at 13:44

0

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.

answered Mar 06 '18 at 13:44

Harsh K

77
1
10

score 0 · Answer 13 · answered Oct 03 '18 at 07:10

0

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.

answered Oct 03 '18 at 07:10

Armin

629
6
23

score 0 · Answer 14 · answered Oct 10 '18 at 12:25

-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.

score 0 · Answer 15 · answered Jul 08 '20 at 09:17

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.

score 0 · Answer 16 · answered Mar 01 '21 at 05:49

0

Worked solution is

Search GoogleToolboxForMa in xcodeproj
Remove all references from the build configurations

answered Mar 01 '21 at 05:49

Krishna Kirana

438
4
10

score -1 · Answer 17 · answered Aug 02 '19 at 07:21

-1

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

answered Aug 02 '19 at 07:21

Shakeel Ahmed

5,361
1
43
34

score -6 · Answer 18 · answered Feb 22 '17 at 10:35

-6

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

answered Feb 22 '17 at 10:35

Ravi Kant

13
2

Do not post whole screenshots, please provide only in-lined portion, my friend. – igraczech Feb 22 '17 at 10:50
This worked, although it would be better to explain the solutions instead of posting the screenshots. The solution is to change the Valid Arch Only to "No" at the project and Pods targets. – Ignacio Barrea May 06 '17 at 21:57

Framework not found GoogleToolboxForMac

18 Answers18

Linked

Related