Problem running the step with a Gemfile with cocoapods

[amorino]

I have this problem running this step.

Determining required cocoapods version
Searching for Podfile.lock
Found Podfile.lock: /Users/vagrant/git/ios/Podfile.lock
Required CocoaPods version (from Podfile.lock): 1.9.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.9.1 gem
Installing
$ gem "install" "cocoapods" "--no-document" "-v" "1.9.1"
Command failed, error: exit status 1

I have no verbose log from gem "install" "cocoapods" "--no-document" "-v" "1.9.1" so that's all I have.

The build is https://app.bitrise.io/build/e01351f600a0a84d if someone can check it.

I ran the command gem "install" "cocoapods" "--no-document" "-v" "1.9.1" from Remote Access successfully.

Some things to have in mind is that I have a Gemfile in the root of the project with cocoapods as dependency and the Podfile is on the folder /ios/, the step doesn't seem to find that Gemfile.

[pigeon-archive]

Hi @amorino,

Can you try doing the same command as a Script step to see if it fails or succeeds? If fails, this could be a bug in the step.

[amorino]

I think resolve the error.

I have a file .ruby-version on ios folder, it always fails because of that, the Bitrise machine doesn't find the correct version. If I run the command from outside of that folder, the command always runs fine. The thing is that the command is running from inside the ios folder because there's the place where the Podfile exists.

It is not a big deal at the end because I found the issue, but is it possible to verbose also what is happening with the gem install command?

[pigeon-archive]

I will create a ticket for the engineering team to look at this at some point in the future.

internal ref: https://bitrise.atlassian.net/browse/TOOL-2338

[aiKrice]

same problem here

[pigeon-archive]

This has not been worked on yet.

[github-actions[bot]]

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

[github-actions[bot]]

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.