[ios] Error "library not found for" after putting application in AdMob

I am getting an error after I put my application in an AdMob. The app was working until today. The error is the following:

ld: library not found for -lGoogleAdMobAds
clang: error: linker command failed with exit code 1 (use -v to see invocation)

How can I fix this? Thank you.

I know this is a bit old, but I just hit a similar issue and running 'pod update' fixed this for me. My library error was with AFNetworking...

Just be careful doing pod update if you don't use explicit versions in your pod file.

Simply, GoogleAdMobAds.a is missing in project target. For me it was libAdIdAccessLibrary.a Please check attached screenshot

Easy solution. Here's how I'd fix the issue:

1. Go to the directory platforms/ios
2. Then, execute the command pod install

That's it. This should install the missing library.

I was getting similar bugs on library not found. Ultimately this is how I was able to resolve it

1. Before starting with Xcode Archive, used flutter build iOS
2. Changed the IOS Deployment Target to a higher target iOS 11.2 . Earlier I had something like 8.0 which was giving all the above errors.
3. Made sure that the IOS deployment targets in Xcode are same in the Project, Target and Pods

This happens if you're using cocoapods, use the .xcworkspace file instead of the default .xcodeproj file.

@raurora's answer pointed me in the right direction. I was including libraries in my "watchkitapp Extension/lib" path. In this case, the Library Search Path needed to be escaped with a '\', but the linker didn't seem to understand this. To fix / work-around the issue, I moved my lib path up one level so it was no longer in a directory that contained a space in the name.

This can also happen if you open project file instead of a workspace. I've wasted like a day myself this way.

Select your Target, go to "Build Phases" in "Link Binary With Libraries" remove ".a" file of that library. Clean and Build.

goto Build Phases -> Link Binary With Libraries and remove library which show errors because that library is not available in project folder

Running 'pod update' in my project fixed my problem with the 'library not found for -lSTPopup' error.

Remarking Trevor Panhorst's answer:

"Just be careful doing pod update if you don't use explicit versions in your pod file."

As for me this problem occurs because i installed Material Library for IOS. to solve this issue

1: Go to Build Settings of your target app.

2: Search for Other linker flags

3: Open the other linker flags and check for the library which is mention in the error.

4: remove that flag.

5: Clean and build.

I hope this fix your issue.

I had a similar "library not found" issue. However it was because I accidentally was using the .xcodeproj file instead of the .xcworkspace file.

I just update the pod file 'pod update' and it start to work for me normally.

If error is like following

ld: library not found for -lpods

I found that a file "libPods.a" which is in red colour(like missing files) was created somehow in the Framework group of the project. I just simply removed that file and everything got fine.

EDIT: Another Solution

Another Solution that I have already answered in the similar question is in this link

In my case there was a naming issue. My library was called ios-admob-mm-adapter.a, but Xcode expected, that the name should start with prefix lib. I've just renamed my lib to libios-admob-mm-adapter.a and fixed the issue.

I use Cocoapods, and it links libraries with Other linker flags option in build settings of my target. The flag looks like -l"ios-admob-mm-adapter"

Hope it helps someone else

This error is very weird.

I had this error with -ldAfnetworking and I only copy my project in other path and works.

Late for the answer but here are the list of things which I tried.So it will be in one place if anyone wants to try to fix the issue.

1. Valid architecture = armv7 armv7s
2. Build Active Architecture only = NO
3. Target -> Build Settings ->Other Linker Flags = $(inherited)
4. Target -> Build Settings ->Library Search Path = $(inherited)
5. Product Clean
6. Pod Update in terminal

For my case Xcode 7, also worked in Xcode 9.1

ld: library not found for -ldAfnetworking
clang: error: linker command failed with exit code 1 (use -v to see invocation)

set Build Active architecture Only to Yes

I tried renaming my build configuration Release to Production, but apparently cocoa pods doesn't like it. I renamed it again to Release, and everything builds just fine.

If error related to Cocoapods as follow:

library not found for -lPod-...

You need to check Other Linker Flags and remove it from there.

Extra Information: If you have an old project that uses cocoapods. And recently you needed to add the use_frameworks! to your podfile. cocoapods will not add the libraries to your Other Linker Flags anymore cause its inherited. Therefore, you may need to remove those manually from the other linker flags which they were added before using the use_frameworks!

It is compile time error for a Static Library that is caused by Static Linker

ld: library not found for -l<Library_name>

1. You can get the error Library not found for when you have not include a library path to the Library Search Paths

ld means Static Linker which can not find a location of the library. As a developer you should help the linker and point the Library Search Paths

```
Build Settings -> Search Paths -> Library Search Paths 
```

2. Also you can get this error if you first time open a new project (.xcodeproj) with Cocoapods support, run pod update. To fix it just close this project and open created a workspace instead (.xcworkspace )

[Vocabulary]

In the case of ld: library not found for -{LIBRARY_NAME} happened because the library file(s) is not existing.

Check the library path on your application targets’ “Build Phases” Library Search Paths tab.

The library file(s) path must be according to the real path for example if your file(s) in the root of the project you must set the path like $(PROJECT_DIR)

1. Cleaned Build Folder
2. Restarted XCode

Went away...