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.

Error: /bin/sh: pod: command not found

See original GitHub issue

As title.

ℹ️  STARTED: "wipe system iOS Pods cache"
error

Task "wipe system iOS Pods cache"
Error: /bin/sh: pod: command not found
.
Exit code: 127

.
Error:

Task "wipe system iOS Pods cache"
Error: /bin/sh: pod: command not found
.
Exit code: 127

Issue Analytics

State:
Created 2 years ago
Reactions:2
Comments:11 (9 by maintainers)

Top GitHub Comments

1reaction

FilipMaslovariccommented, Apr 4, 2022

Yep, 100% agree - the default position should be a bare-bones project, that’s why I was thinking to myself “hmm, I just want it to be able to capture the option of using Bundler 🤔”.

And yep, fork and a PR back to this repo, just want to make sure I am not actually writing garbage first 😅!

1reaction

mikehardycommented, Apr 3, 2022

Think it’s time I forked this project…

Hopefully with PRs back to this repo though, I’ve been recommending it for a couple years now and it’s really handy to have one canonical place to send people.

I understand everything you mentioned, I just want to say that my use case is that I clone the raw react-native template all the time as a react-native release tester, and I use current ruby via rvm. I make sure pod is up to date, and ruby is up to date in my PATH like a good maintainer of environments. I just want react-native to run and use them, personally. I don’t want a full-fledged Ruby dev environment with Gemfiles and all that. So if you make a PR please just consider my use case (which may be summarized as: the way react-native worked from 2018 to 2021)