Error installing cocoapods error failed to build gem native extension

First, check the version of Ruby you are using.

$ruby -v
ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-darwin18]
$ which ruby
usr/bin/ruby

Now use Homebrew to install the latest Ruby.

$ brew install ruby
==> ruby
By default, binaries installed by gem will be placed into:
/usr/local/lib/ruby/gems/2.7.0/bin

You may want to add this to your PATH.

ruby is keg-only, which means it was not symlinked into /usr/local,
because macOS already provides this software and installing another version in
parallel can cause all kinds of trouble.

If you need to have ruby first in your PATH run:

$ echo 'export PATH="/usr/local/opt/ruby/bin:$PATH"' >> /Users/xxx/.bash_profile

For compilers to find ruby you may need to set:

$ export LDFLAGS="-L/usr/local/opt/ruby/lib"
$ export CPPFLAGS="-I/usr/local/opt/ruby/include"

Follow the instructions to set PATH. Now you will go to see the installed Ruby. Make sure to replace the ‘xxx’ with your username.

$ echo 'export PATH="/usr/local/opt/ruby/bin:$PATH"' >> /Users/xxx/.bash_profile
$ echo 'export LDFLAGS="-L/usr/local/opt/ruby/lib"' >> ~/.bash_profile
$ echo 'export CPPFLAGS="-I/usr/local/opt/ruby/include"' >> ~/.bash_profile

$ source ~/.bash_profile

Finally, Make sure your PATH is in place.

$ ruby -v
ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-darwin18]
$ which ruby
/usr/local/opt/ruby/bin/ruby

You’re good to go! Make sure you install by specifying the save destination as follows.

$ sudo gem install -n /usr/local/bin cocoapods

I am getting the same error over and over again and I do not know why. I tried several ways to fix it, but nothing works.

Code Block sudo gem install cocoapods
Building native extensions. This could take a while...
ERROR:  Error installing cocoapods:
	ERROR: Failed to build gem native extension.
    current directory: /Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/ext/ffi_c
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby -I /Library/Ruby/Site/2.6.0 -r ./siteconf20201202-2686-t7m7nb.rb extconf.rb
checking for ffi.h... * extconf.rb failed *
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.
Provided configuration options:
	--with-opt-dir
	--without-opt-dir
	--with-opt-include
	--without-opt-include=${opt-dir}/include
	--with-opt-lib
	--without-opt-lib=${opt-dir}/lib
	--with-make-prog
	--without-make-prog
	--srcdir=.
	--curdir
	--ruby=/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/$(RUBY_BASE_NAME)
	--with-ffi_c-dir
	--without-ffi_c-dir
	--with-ffi_c-include
	--without-ffi_c-include=${ffi_c-dir}/include
	--with-ffi_c-lib
	--without-ffi_c-lib=${ffi_c-dir}/lib
	--enable-system-libffi
	--disable-system-libffi
	--with-libffi-config
	--without-libffi-config
	--with-pkg-config
	--without-pkg-config
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:467:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:585:in `block in try_compile'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:534:in `with_werror'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:585:in `try_compile'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:1109:in `block in have_header'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:959:in `block in checking_for'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:361:in `block (2 levels) in postpone'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:331:in `open'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:361:in `block in postpone'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:331:in `open'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:357:in `postpone'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:958:in `checking_for'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:1108:in `have_header'
	from extconf.rb:10:in `system_libffi_usable?'
	from extconf.rb:42:in `<main>'
To see why this extension failed to compile, please check the mkmf.log which can be found here:
  /Library/Ruby/Gems/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.13.1/mkmf.log
extconf failed, exit code 1
Gem files will remain installed in /Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1 for inspection.
Results logged to /Library/Ruby/Gems/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.13.1/gem_make.out

Something might be wrong with Ruby, but I could not figure out what I should do to fix it.

Accepted Reply

Replies

sudo gem install cocoapods

I’ve installed ruby 2.3.0 but I got the following error:

The text was updated successfully, but these errors were encountered:

Seems like a ruby issue on your system. Please ask in StackOverflow instead.

But wouldn’t it be helpful to at least mention the prerequisites in the docs?

This question has been asked on StackOverflow:

And on AskDifferent, the Apple-specific site on Stack Exchange:

I had the same problem on macOS Mojave 10.14.16

A few threads eventually lead me here which solved it for me:

It looks like CocoaPods 1.9.0, the latest version as of this writing, depends on a newer version of Ruby than 2.3.7. But macOS Mojave only includes Ruby 2.3.7, so you have a few different options.

1. Upgrade to macOS Catalina and get Ruby 2.6.3
2. Use Ruby Version Manager to install a newer version of Ruby
3. Install an older version of CocoaPods
   sudo gem install cocoapods -v 1.8.4

I did 3
sudo gem install cocoapods -v 1.8.4

I was installing Flutter, now flutter doctor says «Xcode — develop for iOS and macOS» is OK.

I had a similar problem for macOS Catalina.
Here is what worked for me:

Hey, so I also had the same problem. This is probably happening because your computer has older version of ruby. So you need to first update your ruby. Mine worked for ruby 2.6.3 version.I got this solution from stackoverflow,

You need to first open terminal and put this code
curl -L https://get.rvm.io | bash -s stable

Then put this command
rvm install ruby-2.6

This would install the ruby for you if it hasn’ t been installed.After this just update the ruby to the new version
rvm use ruby-2.6.3

After this just make ruby 2.6.3 your default
rvm —default use 2.6.3

This would possibly fix your issue. You can now put the command
sudo gem install cocoapods
And the command
pod setup

Источник

Trouble with installing cocoapods

I am getting the same error over and over again and I do not know why. I tried several ways to fix it, but nothing works.

Something might be wrong with Ruby, but I could not figure out what I should do to fix it.

Accepted Reply

Depending on some aspects this might work for you, if you don’t mind using the «SUDO» command:

sudo gem install -n /usr/local/bin cocoapods -v 1.8.4

Latest CocoaPods 1.10.0 won’t work.

Having same issue with my mac, anyone please help.

I really don’t know how to thank you I spent 4 hours trying to solve this problem Thank you with all my heart

Man thanks. You are a lifesaver.

1) Install homebrew via terminal.

2) After homebrew is successfully installed, type in the terminal ‘$ brew install cocoapods’

Thank you my man, it solved my issues 🙂

Thanks. This worked for me

this works for me.

sudo xcode-select —switch /Applications/Xcode-beta.app/Contents/Developer

explain solution
sudo xcode-select —switch

Depending on some aspects this might work for you, if you don’t mind using the «SUDO» command:

sudo gem install -n /usr/local/bin cocoapods -v 1.8.4

Latest CocoaPods 1.10.0 won’t work.

Having same issue with my mac, anyone please help.

I really don’t know how to thank you I spent 4 hours trying to solve this problem Thank you with all my heart

Man thanks. You are a lifesaver.

Thank you all ! With sudo gem install cocoapods it worked!

Same problem — XCode 12.3 on Mac OS 10.15.6.

Tried the CocoaPod mac app from the CocoaPods about page, which did have an option to install the command line tool, but it was version 1.1.x for some reason.

Brew install did the trick, and installed 1.10.0.

how’d you get it to install 1.10.0, a detailed explanation would be desperately appreciated thank you. Ive been at it for 2/3 days straight on installing the latest version for my project

hai @ Me -Human has your problem been solved?

am having the same problem , using: brew install cocoapod , would install version 1.5 and I need version 1.10 even when I tried brew it installed version 1.5. every time I upgrade , it gives me same error msg:

Источник

Today when I configuring the Flutter development environment on Mac OS, according to flutter doctor command, I want to use the following command to install cocoapods:

sudo gem install cocoapods

But I got an error message:

Building native extensions. This could take a while...
ERROR:  Error installing cocoapods:
	ERROR: Failed to build gem native extension.

    current directory: /Library/Ruby/Gems/2.6.0/gems/ffi-1.14.2/ext/ffi_c
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby -I /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0 -r ./siteconf20210222-12879-1feqcae.rb extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
	--with-opt-dir
	--without-opt-dir
	--with-opt-include
	--without-opt-include=${opt-dir}/include
	--with-opt-lib
	--without-opt-lib=${opt-dir}/lib
	--with-make-prog
	--without-make-prog
	--srcdir=.
	--curdir
	--ruby=/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/$(RUBY_BASE_NAME)
	--with-ffi_c-dir
	--without-ffi_c-dir
	--with-ffi_c-include
	--without-ffi_c-include=${ffi_c-dir}/include
	--with-ffi_c-lib
	--without-ffi_c-lib=${ffi_c-dir}/lib
	--enable-system-libffi
	--disable-system-libffi
	--with-libffi-config
	--without-libffi-config
	--with-pkg-config
	--without-pkg-config
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:467:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:546:in `block in try_link0'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/tmpdir.rb:93:in `mktmpdir'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:543:in `try_link0'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:570:in `try_link'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:672:in `try_ldflags'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:1832:in `pkg_config'
	from extconf.rb:9:in `system_libffi_usable?'
	from extconf.rb:42:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /Library/Ruby/Gems/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.14.2/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in /Library/Ruby/Gems/2.6.0/gems/ffi-1.14.2 for inspection.
Results logged to /Library/Ruby/Gems/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.14.2/gem_make.out

I searched many places according to the keywords of this error message, and tried various methods such as upgrading the version and adjusting the path, but still no solution. Finally, it was mentioned in a forum discussion that «Recommended not to use the ruby that comes with Mac OS to install the package«.

So, I tried to switch the ruby version and reinstall it, this time it succeeded.

Solution

Install Ruby Version Manager (RVM):

curl -L https://get.rvm.io | bash -s stable
source ~/.rvm/scripts/rvm
rvm list known

Output:

# MRI Rubies
[ruby-]1.8.6[-p420]
[ruby-]1.8.7[-head] # security released on head
[ruby-]1.9.1[-p431]
[ruby-]1.9.2[-p330]
[ruby-]1.9.3[-p551]
[ruby-]2.0.0[-p648]
[ruby-]2.1[.10]
[ruby-]2.2[.10]
[ruby-]2.3[.8]
[ruby-]2.4[.10]
[ruby-]2.5[.8]
[ruby-]2.6[.6]
[ruby-]2.7[.2]
[ruby-]3[.0.0]
ruby-head

In the examples I saw, the installation of 2.5.x and 2.6.x were successful.

Based on the higher the version the better, I chose 2.6.6 to install.

rvm install 2.6.6

After installation, you can use the following command to check ruby version, make sure that the current ruby version is you just installed.

ruby -v

Output:

ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-darwin19]

Use the following command again:

sudo gem install cocoapods

Then you can install it normally.

References

• https://rvm.io/
• https://medium.com/%E5%BD%BC%E5%BE%97%E6%BD%98%E7%9A%84-swift-ios-app-%E9%96%8B%E7%99%BC%E6%95%99%E5%AE%A4/sudo-gem-install-cocoapods-show-failed-to-build-gem-native-extension-error-handling-9956a4e71385
• https://stackoverflow.com/questions/20939568/error-error-installing-cocoapods-error-failed-to-build-gem-native-extension

Read More

• [Solved] urllib.error.URLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed

If you are using Unity to build your iOS projects and use SDK’s like Firebase, Facebook etc. which require CocoaPods, then these steps enlisted below should help you run a smooth and successful build.

Even if you are not using Unity and just using Xcode project, these steps should ensure that the pods get installed in your project successfully.

Once everything is setup, the builds usually almost always run successfully and rarely give problems. It is mostly during the first build or sometimes after an OS update or after a hard disk change or moving to a new machine, that problems creep up and the Unity build fails with the message – “iOS framework addition failed due to a Cocoapods installation failure. This will will likely result in an non–functional Xcode project.“. It is a long error message in the Console which would probably state how even the “pod repo update” was attempted and it failed as well.

For the people who aren’t aware how Pods work and not familiar with the Xcode CocoaPods workflow, this error is very hard to decipher and fix.

If you have encountered this error, follow the steps below to fix it and setup CocoaPods correctly.

The setup used for the purpose of this writeup:

MacOS Catalina (10.15.6)

Unity 2018.4.22f1

Xcode 11.4.1

CocoaPods 1.9.1 

1) Install Xcode. 

Pretty self explanatory and in all probability you should have done this step already. Xcode can be installed from the Mac AppStore or by downloading a xip file from the apple developer site.

2) Sudo xcode-select

Now we have to ensure that our system knows where our Xcode is and specifically where the developer tools which come bundled with it are installed.

Open Terminal on your Mac and run the following command.

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

Please note that the path to Xcode on your machine may vary. The path listed above is the default location of Xcode. You may have installed or moved Xcode to a new location. In that case, please run the command with the appropriate path.

Sometimes, just this magic command can make your build run fine. If it doesn’t, follow the next steps to install and correctly setup CocoaPods on your system.

3) CocoaPods installation and setup.

If your build is failing, the most likely cause is that CocoaPods is not installed and setup properly. So follow the steps below and by the end of it, CocoaPods would be installed successfully on your system.

First lets remove any previous installations so that we can make a fresh start. Open a Terminal and run the command below. If there was a previous installation (or more than one installations) this will remove them. Type “y” and press “Enter/Return” on any prompts that this command makes.

sudo gem uninstall cocoapods

Once you have uninstalled the previous version (or if no previous version exists) proceed to install cocoapods. Run the following command on the Terminal.

sudo gem install cocoapods

Let the process complete successfully. This should install the latest version of CocoaPods on your system.

But the installation process isn’t complete. CocoaPods is basically a repository of frameworks and their dependencies. You just have to specify which “pods” you want in your project in a podfile and it installs them. But in order for it to work, the entire repository needs to be on your system in a specific folder. There are several ways to do that. The first time you run a pod install, it will download the repository before proceeding. In older versions of CocoaPods, you can run pod setup and it should do the job (since version 1.8.0, pod setup does nothing!). Or in some cases pod repo update might work. 

But I am going to list the method that I use which works for me every time.

First we need to create a folder. Go to your user folder using Finder Explorer. Look for a folder name .cocoapods. (It is a hidden folder since the name starts with a dot). If you can’t see the folder, press Command+Shift+. to reveal the hidden folders. If the folder doesn’t exist, then create one with the name. Open the folder and look for a folder named repos. If the folder doesn’t exist, create one by that name. Open the repos folder. If there is a master folder inside it, then delete it. We are going to recreate it. Your folder structure should look like this :

Once you have got this open the terminal and run the below commands one by one.

cd ~/.cocoapods/repos

git clone --depth 1 https://github.com/CocoaPods/Specs.git master

pod repo update

The git command should take a few minutes to complete as it downloads the repository to your system. Ensure all the commands listed above are completed successfully. Your folder structure should look like this.

Voila! Now you have completed the installation correctly. Go back to Unity and build for iOS again. And this time the build should succeed without any errors!

4) Use .xcworkspace file instead of .xcodeproj

If you are new to using Pods, then you probably won’t even be aware of this. If you are experienced, there is still a chance that you might forget this.

Always, use the .xcworkspace file to open your project in Xcode and not the .xcodeproj which you are probably used to.

Once the unity build process completes and the pods are installed successfully, notice that the generated Xcode project now has a .xcworkspace file alongside the usual .xcodeproj file. Use the .xcworkspace file to open you project in Xcode. Using the .xcodeproj file to open the project will lead to errors when building the Xcode project.

4a) There is no .xcworkspace file in my Xcode project!

Relax. This may not be a problem. Unity also has the ability to load pods from .xcodeproj file as well. The External Dependency Manager used by Unity to manage pods has the option to add pods to either to the workspace or the project file as shown in the image below. Check which setting you are using by going to the following location in Unity.

Assets -> External Dependency Manager -> iOS Resolver -> Settings 

If there is no workspace file in your project, try building the project using the .xcodeproj file. If it doesn’t work, try changing the iOS Resolver Setting and generate a .xcworkspace file.

5) Keep CocoaPods updated.

Everything might work correctly for some time and then suddenly you might face the pod installation error again. This might be because the repo could not be updated due to some error. Try running the ‘pod repo update’ command manually again and see if it helps.

Also it might be possible that your CocoaPods version is outdated and one or more of your pods require a higher version of CocoaPods. In that case, just run the below command (same command which was used for installing) and it will update you CocoaPods to the latest version. 

sudo gem install cocoapods

There is a strange bug currently if you are using Unity + Firebase where the Xcode build will fail with error –

Unable to read Google Service plist at path….

This error is surprisingly being caused because of spaces in build folder name! To fix this error, just rename your build folder without any spaces and then run the build again. It should run successfully now.

Refer to below links:

https://github.com/firebase/quickstart-unity/issues/557

https://github.com/firebase/quickstart-unity/issues/714

Some parting info on CocoaPods

There’s a lot of information on CocoaPods out on the internet, some old some new. A lot of questions being answered on StackOverflow. If you have been going through all the material, it can cause quite a lot of confusion. Especially with the new versions of CocoaPods not requiring the master repository on your system. Let me help you out with that.

As of CocoaPods version 1.8.0, there is no mandatory requirement for the master repository on your system. However, this also requires a change in the projects podfile to change the source of download. When testing with Unity 2018.4.22f1, I found the podfile still tries to download from the master repository and hence the master repo is required on the system. If the repo is not present, the Unity build process will try to download and install the repo which may fail due to network issues or some other error and will cause the build to fail. So it is better to have the master repository for now. In the future, when the new methodology is stable and becomes the norm, we probably won’t need the master repository.

When running into issues, a lot of old answers on internet can point you to “pod setup”  to solve the problem. Let me reiterate that as of version 1.8.0, this command does nothing and just prints a completed message. Hence don’t rely on it.

“pod repo update” command can be run to keep the master repo updated but it requires the master repository correctly configured to work. It especially requires the .git folder inside the master folder to be configured correctly. This command can be run on Terminal from any folder.

“pod install” command is used to install the pods in your project. It will also download and install the master repository if it is not present. This command can only be run from a folder which has a valid podfile.

Hopefully you won’t run into any issues if you follow the above mentioned steps correctly and won’t need any additional help.

I am no expert on CocoaPods. But I have had to fiddle around to get my project to build with Google Firebase SDK and Facebook SDK. Hopefully this writeup will help any one else coming across the same problems.