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 if pod 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 in runPodInstall it uses bundle exec pod install instead.
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
I've noticed that as part of recent update to CLI,
run-iosbuilds CocoaPods dependencies.There seems to be a bit of inconsistency because in
installPodsCLI checks ifpodcommand is available (https://github.com/react-native-community/cli/blob/a856ce027a6b25f9363a8689311cdd4416c0fc89/packages/cli-config-apple/src/tools/installPods.ts#L154C7-L154C18) and shortly after inrunPodInstallit usesbundle exec pod installinstead.I can see that some other parts of CLI use
podCLI directly (await execa('pod', ['cache', 'clean', '--all'], andawait execa('pod', ['repo', 'update']);) but wouldn't it make more sense to always callpodthroughbundle exec?Up until today I didn't need global
podCLI installed on my machine as I was always usesbundleinstead