Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with CocoaPods

See original GitHub issue

Hi,

tns doctor returns that there is an issue with CocoaPods:

[!] Oh no, an error occurred.

Search for existing GitHub issues similar to yours:
https://github.com/CocoaPods/CocoaPods/search?q=Operation+not+permitted+-+curl&type=Issues

If none exists, create a ticket, with the template displayed above, on:
https://github.com/CocoaPods/CocoaPods/issues/new

Be sure to first read the contributing guide for details on how to properly submit a ticket:
https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md

Don't forget to anonymize any private data!


[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `__PROJECT_NAME__` to `Pods/Target Support Files/Pods-__PROJECT_NAME__/Pods-__PROJECT_NAME__.debug.xcconfig` or include the `Pods/Target Support Files/Pods-__PROJECT_NAME__/Pods-__PROJECT_NAME__.debug.xcconfig` in your build configuration (`__PROJECT_NAME__/build-debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `__PROJECT_NAME__` to `Pods/Target Support Files/Pods-__PROJECT_NAME__/Pods-__PROJECT_NAME__.release.xcconfig` or include the `Pods/Target Support Files/Pods-__PROJECT_NAME__/Pods-__PROJECT_NAME__.release.xcconfig` in your build configuration (`__PROJECT_NAME__/build-release.xcconfig`).

WARNING: There was a problem with CocoaPods
Verify that CocoaPods are configured properly.
There seem to be issues with your configuration.

My environment:

MacOSX El Capitan 10.11.5 (15F34)
NodeJS 5.14
Xcode 6.3.1 Build version 6D1002

Let me know if additional details are needed.

Issue Analytics

State:
Created 7 years ago
Comments:16 (7 by maintainers)

Top GitHub Comments

4reactions

codetinkercommented, Dec 4, 2016

I had almost similar problem. Run this command fixed my problem

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

0reactions

sudhanshu-15commented, Nov 16, 2016

NativeScript uses the sandbox-pod executable. This may prevent some pods from installing correctly. If you encounter such cases, you can switch to the regular pod executable: +> +> 1. Open the NativeScript CLI configuration file, usually located in /usr/local/lib/node_modules/nativescript/config/config.json. +> 1. Change the value of USE_POD_SANDBOX to false.

This worked for me.

https://github.com/NativeScript/docs/pull/259/files

Top Results From Across the Web

Issues · CocoaPods/CocoaPods - GitHub

Pod::StandardError - [Bug] Unable to find the specification for (from ../node_modules/expo-modules-core/ios ) . ... CardIO import in Swift Framework creates ...

Troubleshooting - CocoaPods Guides

<Using the CocoaPods Project · Check if the pod header files are correctly symlinked in Pods/Headers and you are not overriding the HEADER_SEARCH_PATHS...

issue with cocoapods installation | Apple Developer Forums

this works for me: Step 1 (install HomeBrew). /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh).

Issues with CocoaPods. The most common problems I run into…

The most common CocoaPods errors: No such module, Compiled with optimization, and library versions.

Failing to add pod file to Xcode 13 project - Stack Overflow

The version of CocoaPods used to generate the lockfile (1.11. 2) is higher than the version of the current executable (1.10. 1).