Debug a CocoaPods pod install failure with verbose output
Use verbose output to find the first failing download, resolver, Ruby, or Xcode integration step before cleaning caches.
Use verbose output to find the first failing download, resolver, Ruby, or Xcode integration step before cleaning caches.
Try these fixes in order
Record environment
Note pod --version, Ruby version, Xcode selection, and whether the project uses Bundler.
pod --versionRun with detail
From the Podfile directory, rerun install with verbose output. Redact private URLs and tokens before sharing logs.
pod install --verboseClassify the failure
A spec resolution error needs source or version changes; a download failure needs network or credentials; an integration failure needs project inspection.
Apply a narrow fix
Retry the same install after correcting the first cause, then compare Podfile.lock and the generated workspace.
Interpret what you see
Verbose output fails while fetching a pod
What it suggests: The problem is source availability or authentication.
Next check: Record the first URL and check access; redact tokens before sharing logs.
Resolution succeeds but integration fails
What it suggests: The download cache is probably not the cause.
Next check: Inspect Xcode project configuration and the first integration error.
A Ruby exception appears before dependency work
What it suggests: The CocoaPods installation or plugin environment may be broken.
Next check: Compare pod, Ruby, Bundler, and plugin versions in the failing shell.
Why this happens
- Dependency resolution or download fails.
- Ruby tooling or Xcode project integration fails later.
Still not working?
Avoid running CocoaPods as root as a blanket fix; permission problems should be traced to the specific files and installation method.
Official sources
These steps are based on the linked documentation and general diagnostics. BugMedic has not independently tested every product and system configuration. Review commands before running them.