• [ x] I've read and understood the CONTRIBUTING guidelines and have done my best effort to follow.

Report

TL;DR Work-around

Install from gem instead of brew, via gem install cocoapods per related #6778

What did you do?

Tried to run cocoapods on Mac 10.15, from a Brew based installation

type pod

What did you expect to happen?

Brew based cocoapods installer should link to available "Current" Ruby version, instead of falling back to 2.3, which hasn't been available for a while.

What happened instead?

Brew defaulted to using unavailable Ruby 2.3, as in the case of the related High Sierra bug:

Fails with following one-line error message
/usr/local/Cellar/cocoapods/1.7.3/bin/pod: /usr/local/Cellar/cocoapods/1.7.3/libexec/bin/pod: /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby: bad interpreter: No such file or directory
/usr/local/Cellar/cocoapods/1.7.3/bin/pod: line 2: /usr/local/Cellar/cocoapods/1.7.3/libexec/bin/pod: Undefined error: 0

CocoaPods Environment

Mac 10.15 / Catalina
Brew based cocoapods - defaults to 2.3, instead of "Current"

This won't run due to reliance on deprecated Ruby 2.3 which does not exist on later Mac versions.

Project that demonstrates the issue

Base Mac 10.15 install, install / upgrade cocoapods, then try to run