Yes, CocoaPods can’t fix API breaking changes, but as we use semantic-versions and encourage authors to follow those, it can at least be mitigated more easily. E.g. A version requirement of: ‘~> 1’ should then install the latest v1.x.x, but not v2 which has API breakage.
Obviously this is not fool-proof and many are still getting used to it.
Obviously this is not fool-proof and many are still getting used to it.