You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see that some other parts of CLI use pod CLI directly (await execa('pod', ['cache', 'clean', '--all'], and await execa('pod', ['repo', 'update']);) but wouldn't it make more sense to always call pod through bundle exec?
Up until today I didn't need global pod CLI installed on my machine as I was always uses bundle instead
The text was updated successfully, but these errors were encountered:
I've noticed that as part of recent update to CLI,
run-ios
builds CocoaPods dependencies.There seems to be a bit of inconsistency because in
installPods
CLI checks ifpod
command is available (https://github.com/react-native-community/cli/blob/a856ce027a6b25f9363a8689311cdd4416c0fc89/packages/cli-config-apple/src/tools/installPods.ts#L154C7-L154C18) and shortly after inrunPodInstall
it usesbundle exec pod install
instead.I can see that some other parts of CLI use
pod
CLI directly (await execa('pod', ['cache', 'clean', '--all']
, andawait execa('pod', ['repo', 'update']);
) but wouldn't it make more sense to always callpod
throughbundle exec
?Up until today I didn't need global
pod
CLI installed on my machine as I was always usesbundle
insteadThe text was updated successfully, but these errors were encountered: