When will there be a next release after 1.12.1?

[beretboat]

I'm really looking forward to the Xcode 15 fix.

[ghost]

Good morning any news on this?

[vesper8]

I couldn't wait so I just installed the master and it's working!

Here's how I did that

sudo gem install specific_install
sudo gem specific_install https://github.com/CocoaPods/CocoaPods.git

[twiedow]

Any news on this?

[CodingMarkus]

In the meantime, just open a Terminal window and run

find . -type f -exec grep -l 'DT_TOOLCHAIN_DIR' {} \; | while IFS= read -r file; do sed -i '' 's/DT_TOOLCHAIN_DIR/TOOLCHAIN_DIR/g' "$file"; done

After that the error is gone and won't return unless you run pod update or pod install again, in which case you must run that command again.

[ghost]

@dnkoutso is it possible to release this?

[india2sarthak]

@dnkoutso Any update on this? Xcode 15 has officially been released, hence this going to be an issue concerning a lot of folks now. I hope the release is planned soon. Thanks!

[fampaySiddharth]

Any updates? If not we could probably add a note to the Readme.md itself for now for the possible hotfixes.

[skywalkerlw]

Same question, any update?

[LiamJTF]

Yeah same question

[arivas87]

Xcode 15 is already released and we don't have a fully compatible CocoaPods version...

[ghost]

For those who are using bundler I found this that helped in my case:

#12009 (comment)

[soucolline]

I don't understand the lack of communication from the maintainers on this topic. At least we should have a message that it's being taken into account and an approximate date so we can act accordingly on our projects

[tsfischer]

Honestly I think Cocoapods is dead. We've been slowly moving off of it for some time, since SPM is obviously the future, but I didn't know it was going to just outright break and be unsupported like this.

[jonathanellis]

While app developers have a choice about which package manager they'd like to use, we can't really afford to just have Cocoapods simply die overnight or lag behind in critical updates, because it is integral to cross-platform technologies like Flutter, React Native and Kotlin Multiplatform...

I appreciate this is a community-maintained OSS project so I don't feel it's fair to berate the maintainers - but given that this issue also breaks Flutter and KMM (and possibly React Native?), I think the dependency on Cocoapods should perhaps be re-evaluated...

The lack of a release to resolve this Xcode 15 issue, almost 2 months after the beta release which caused this, and days after the production release is really rather concerning 😔

[LiamJTF]

I dont see why they are taking so long to respond to all of this, they simply need to made a build, not even a major, build it can simply be 1.12.2 with just a fix for this issue that is a major thing, sure there are simple fixes but we shouldnt be resorting to hacky methods that doesnt apply to everyone when they could release a permanent fix. smh my head 🤪

[CodingMarkus]

Honestly I think Cocoapods is dead.
We've been slowly moving off of it for some time, since SPM is obviously the future

SPM can only distribute Swift code (or mixed code but there always must be Swift in it and mixed code in Swift packages is PITA), the vast majority of Pods are still pure Obj-C pods and the vast majority of app developers still use Obj-C, even when mixing it with Swift code but very little projects out there that use CocoaPods are pure Swift projects, thus SPM is no replacement for CocoaPods for the vast majority of users at the moment and any foreseeable future.

The only real alternative to CocoaPods is Carthage, which uses a more permanent stable approach by not modifying Xcode projects/workspaces and not integrating anything at all, thus being completely independent of changes to the Xcode project format and relatively independent from changes to the Xcode build process. Carthage just downloads the packages, builds them once according to your development/deployment needs and then it's up to you to integrate them into your Xcode project, e.g. by adding the frameworks yourself to the project and also add them to the build phases as required. Usually this only needs to happen once for every new dependency, even if you later on update and rebuild that dependency using Carthage.

So Carthage is more setup work initially, but less likely to ever break once you have a working setup and can be integrated in any non-standard build process, as it relies on nothing and makes no assumption how you build or ship your software at all (e.g. also works fine if your entire Xcode build process is calling make on a Makefile and not using Xcode's dependency system for anything).

[tsfischer]

SPM is no replacement for CocoaPods for the vast majority of users at the moment and any foreseeable future.

"foreseeable future"? That's where I disagree. The writing has been on the wall regarding the future of Obj-C for years now. We've completely removed it from the project I primarily work on now, as it was holding us back from using modern Swift features in the rest of the app (compiler would complain 'you can't use that feature in an @objc object). I've been in this Apple development game for decades and watched the same thing happen with Carbon vs Cocoa. Apple said "Carbon isn't a temporary solution, we'll support it permanently". And they did, until they didn't. If you're long-term strategy includes Obj-C code I think you might want to reevaluate it.

That said, we're off topic here. They already have a fix for Cocoapods, and have for months. The fact that nobody has released it yet, or even commented on it tells me nobody is minding the store here. And that's really scary. Just went through the same thing with SwiftyJSON... a library that was once very popular but the devs just walked away from.

[anushshenoy]

@dnkoutso would appreciate any insight into when the next release is planned. Apologies if I have tagged incorrectly

[dnkoutso]

I am doing this right now, it will take a bit of time but I expect it in the next 1-3 hours.

Closing this as its been worked on.

[india2sarthak]

Thanks! @dnkoutso

[anushshenoy]

Thanks a ton @dnkoutso. Much appreciated

[CristinaAndolfatto]

In the meantime, just open a Terminal window and run

find . -type f -exec grep -l 'DT_TOOLCHAIN_DIR' {} \; | while IFS= read -r file; do sed -i '' 's/DT_TOOLCHAIN_DIR/TOOLCHAIN_DIR/g' "$file"; done

After that the error is gone and won't return unless you run pod update or pod install again, in which case you must run that command again.

This also worked for me! Many many thanks :)