ld: library not found for -lPods-AppName / framework not found Pods_App
The linker can’t find the CocoaPods library — usually because the .xcodeproj was opened instead of the .xcworkspace, or pods weren’t built.
library not found for -lPodsframework not found Pods_ld: library not found for -l Meaning
CocoaPods integrates via the workspace. Building the bare project, missing pod install after cloning, or a mismatched Pods configuration leaves the Pods library absent.
Common causes
- Opened .xcodeproj instead of .xcworkspace
- pod install not run after clone/branch switch
- Deployment target/architecture settings excluding Pods
⚡ Quick fix
- Open .xcworkspace
- pod deintegrate && pod install
- Clean build folder (Shift+Cmd+K)
Detailed fix by platform
Shell
- swift
pod deintegrate && pod install open MyApp.xcworkspace
How to diagnose
- File — Workspace opened?
- Pods — Pods/ folder and Pods.xcodeproj exist?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- built for iOS, linking for simulator Building for iOS Simulator, but linking in object file built for iOS, for architecture arm64
- CDN: trunk URL couldn't be downloaded [!] CDN: trunk URL couldn't be downloaded: https://cdn.cocoapods.org/...
- CocoaPods compatible versions CocoaPods could not find compatible versions for pod
Most viewed in iOS
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026