If this solution does not work for you or you don't want to fiddle in files that are not part of your project (and hence could break other things in the future), then there is another solution which is to downgrade the xcode command line tools to 14.2 or do a similar downgrade in xcode cloud, more details about alternative solutions can be found here: https://stackoverflow.com/questions/75486713/upgrade-from-xcode-14-2-to-14-3-phasescriptexecution-failed-with-a-nonzero-exit/75842910#75842910

I updated my stackoverflow ticket with more info regarding this problem: https://stackoverflow.com/questions/75486713/upgrade-from-xcode-14-2-to-14-3-phasescriptexecution-failed-with-a-nonzero-exit/75842910#75842910

for cloud a workaround is to downgrade the xcode version that is being used, from 14.3 (default version as of now) to 14.2, check out my stackoverflow response for a more detailed answer with screenshots: https://stackoverflow.com/questions/75486713/upgrade-from-xcode-14-2-to-14-3-phasescriptexecution-failed-with-a-nonzero-exit/75842910#75842910

On the 18th of April 2023 the new CocoaPods version 1.12.1 got finally released 🥳 and it includes the fixes needed to solve the problem that this discussion is about: https://github.com/CocoaPods/CocoaPods/releases/tag/1.12.1