Cocoapods: LoadError - cannot load such file -- nanaimo

Created on 30 Mar 2018  Â·  13Comments  Â·  Source: CocoaPods/CocoaPods

Report

What did you do?

ℹ Please replace these two lines with what you did.
e.g. Run pod install

What did you expect to happen?

ℹ Please replace these two lines with what you expected to happen.
e.g. Install all pod dependencies correctly.

What happened instead?

ℹ Please replace these two lines with of what happened instead.
e.g. Pod A is missing the subspec B for target C.

CocoaPods Environment

ℹ Please replace these two lines with the output of pod env.
e.g. via pod env | pbcopy

Project that demonstrates the issue

ℹ Please link to a project we can download that reproduces the issue.
You can delete this section if your issue is unrelated to build problems,
i.e. it's only an issue with CocoaPods the tool.

Most helpful comment

Hello,

The same thing happens to me.

I solved that uninstalling all versions of cocapods and nanaimo. Every gem uninstall command I set to remove all versions.
In order of commands:

gem uninstall cocoapods
gem uninstall -i /Users/cotrim/.rvm/gems/ruby-2.2.1@global cocoapods -> Removing from global gems

than:
gem uninstall nanaimo
gem uninstall -i /Users/cotrim/.rvm/gems/ruby-2.2.1@global nanaimo -> Again, removing from global.

and last step:
gem install cocoapods -> This last step install nanaimo and cocoapods.

now, pod install works. 😄

I Hope have helped you.

All 13 comments

Try gem install nanaimo first.

Please fill in the template and additionally use StackOverflow using cocoapods tag for these questions.

all time error

On 30 Mar 2018, at 09:30, Dimitris Koutsogiorgas notifications@github.com wrote:

Closed #7566 https://github.com/CocoaPods/CocoaPods/issues/7566.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/CocoaPods/CocoaPods/issues/7566#event-1549340019, or mute the thread https://github.com/notifications/unsubscribe-auth/AFN1oWyL-VHfRY6A-OMXR_6hNZWzQz21ks5tjd8ZgaJpZM4TBZET.

Hello Erison,

Did you find any solution for the problem? As I have same set of errors on installation of pod for a Xcode project.

Let me know if you find any solution.

Thanks

Hey Erison,

Seems there is problem with the version of cocoa pod for as we were using version 1.4.0 but after using command
$ [sudo] gem install cocoapods --pre

from link:
https://guides.cocoapods.org/using/getting-started.html#getting-started

worked out and it is currently working fine.

Thanks

Hi

Thank you can solve the problem using using this command sudo gem install cocoapods —pre

On 1 Apr 2018, at 14:10, meAbhishekTripathi notifications@github.com wrote:

Seems there is problem with the version of cocoa pod for as we were using version 1.4.0 but after using command
$ [sudo] gem install cocoapods --pre

Hello,

The same thing happens to me.

I solved that uninstalling all versions of cocapods and nanaimo. Every gem uninstall command I set to remove all versions.
In order of commands:

gem uninstall cocoapods
gem uninstall -i /Users/cotrim/.rvm/gems/ruby-2.2.1@global cocoapods -> Removing from global gems

than:
gem uninstall nanaimo
gem uninstall -i /Users/cotrim/.rvm/gems/ruby-2.2.1@global nanaimo -> Again, removing from global.

and last step:
gem install cocoapods -> This last step install nanaimo and cocoapods.

now, pod install works. 😄

I Hope have helped you.

@cotrim149 thank you very much! Success solved my problem.

Thanks @cotrim149

Ty @cotrim149 , legendary.

Thanks @cotrim149, it works for me

I followed the steps listed above but am still having the same issue. To clarify, I'm running fastlane to install pods in a project. pod install works correctly from the terminal, but calling fastlane cocoapods fails with errors stating:
LoadError - cannot load such file -- nanaimo

@ccChucker
try put the commands in a .sh script and make fastlane call it.

And you are using the rubi version from mac, re-installed ruby version (removed the pre-installed ruby and installed using brew) or rbenv ?

My problem was fixed by uninstalling and re-installing npm. I'm now using bundler and this seems to be much better now.

Was this page helpful?
0 / 5 - 0 ratings