Build error on pods install step

Bitrise Build Issue Report template

Description of the issue

I imported a repo for the first time in bitrise and just followed all the default steps for the instalation but the project did not break.
Its a react native project, building the IOS version.
The key error message is this one:

$ pod "_1.10.1_" "install" "--no-repo-update" "--verbose"
[!] Invalid `Podfile` file: cannot load such file -- /Users/vagrant/git/node_modules/react-native/scripts/react_native_pods.
 #  from /Users/vagrant/git/ios/Podfile:1

Maybe I need to follow some specific steps that I’m not aware of, I was really just hoping the project would build just by importing without any changes

Environment:

Where did the issue happen?

Bitrise.io:
Stack used:
Xcode 12.4.x, on macOS 10.15.7 (Catalina)

Which build Step causes the issue and which version of the step?

| (6) cocoapods-install@1                                                      |
+------------------------------------------------------------------------------+
| id: cocoapods-install 

Reproducibility

Sign up to Bitrise, import project from gitlab, setup with default settings

Local reproduction

Can it be reproduced on your own Mac/PC…
No, on my local machine the build it works both on xcode directly and also using fastlane

Local reproduction: Linux / Android (docker based) stack builds

Does not break locally, just on bitrise

Build log

Please see the build log here:

+------------------------------------------------------------------------------+

| (6) cocoapods-install@1                                                      |
+------------------------------------------------------------------------------+
| id: cocoapods-install                                                        |
| version: 1.11.0                                                              |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2021-04-22T12:33:45+01:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
INFO[12:33:45]  * [OK] Step dependency (go) installed, available. 
Configs:
- SourceRootPath: /Users/vagrant/git
- PodfilePath: 
- IsUpdateCocoapods: false
- InstallCocoapodsVersion: 
- Verbose: true
- IsCacheDisabled: false
Searching for Podfile
Found Podfile: /Users/vagrant/git/ios/Podfile
Determining required cocoapods version
Searching for Podfile.lock
Found Podfile.lock: /Users/vagrant/git/ios/Podfile.lock
Required CocoaPods version (from Podfile.lock): 1.10.1
Searching for gem lockfile with cocoapods gem
No gem lockfile with cocoapods gem found at: 
Using system installed CocoaPods version
Check selected Ruby is installed
Ruby 2.6.5 is installed
Installing cocoapods
Checking cocoapods 1.10.1 gem
Installing
$ gem "install" "cocoapods" "--no-document" "-v" "1.10.1"
$ rbenv "rehash"
cocoapods version:
$ pod "_1.10.1_" "--version"
1.10.1
Installing Pods
$ pod "_1.10.1_" "install" "--no-repo-update" "--verbose"
[!] Invalid `Podfile` file: cannot load such file -- /Users/vagrant/git/node_modules/react-native/scripts/react_native_pods.
 #  from /Users/vagrant/git/ios/Podfile:1
 #  -------------------------------------------
 >  require_relative '../node_modules/react-native/scripts/react_native_pods'
 #  require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
 #  -------------------------------------------
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:318:in `rescue in block in from_ruby'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:312:in `block in from_ruby'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:50:in `instance_eval'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:50:in `initialize'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:310:in `new'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:310:in `from_ruby'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:276:in `from_file'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/config.rb:205:in `podfile'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/command.rb:160:in `verify_podfile_exists!'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/command/install.rb:46:in `run'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/command.rb:52:in `run'
/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/cocoapods-1.10.1/bin/pod:55:in `<top (required)>'
/Users/vagrant/.rbenv/versions/2.6.5/bin/pod:23:in `load'
/Users/vagrant/.rbenv/versions/2.6.5/bin/pod:23:in `<main>'
Command failed, error: exit status 1, retrying without --no-repo-update ...
$ pod "_1.10.1_" "repo" "update"
Updating spec repo `master`
  $ /usr/local/bin/git -C /Users/vagrant/.cocoapods/repos/master fetch origin --progress

Hello @gabefetchly :wave:

There was an issue with cocoapods on Bitrise, for which but we have recently deployed a fix.
Can you let us know if you still experience this issue? If you do, can you please enable Support Access on the Settings tab of the app ( Enabling the Bitrise Support user for your app | Bitrise DevCenter ) so that we can take a more in-depth look? :slight_smile:

Thanks Roland this was a very old issue I got solved already, unfortunately don’t remember how to help others, but I guess was starting fresh again.

Probably unrelated but maybe not, lately I found that it also helps to use the default ruby from bitrise, another project was having issues using ruby 2.7.2 configured on the .ruby-version file on the project root.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.