CocoaPods support

[chrisvasselli]

CocoaPods support

[mattmassicotte]

Yeah it really does. I think in this case, one single package is failing to build, and Xcode does a horrible job of communicating that via this particular view. I've gotten really good at diagnosing and dealing with SPM issues, just like in the past I was good at doing that with Carthage.

I just want to be really clear: I'm not saying it is better at all. I've just accepted our new overlords 😬

[mattmassicotte]

I really hear you on this. It was very painful migrating from Carthage to SPM, and I still miss some features sometimes.

But, the thing is, at this point, I feel like the ship has sailed. Many big projects are dropping support for other dependency management systems if they had it, and Apple themselves (of course), publish many packages as SPM-only.

All that said, if you want to put together and maintain a podspec,, I will publish it!

[chrisvasselli]

Yeah, I get it. But then I am forced to nuke my derived data folder one more time, and waste one more hour dealing with obscure errors, and I am reinvigorated to go down with the ship. 😅

I'll put together a podspec. 👍

[mattmassicotte]

Go for it! While I (nearly) never have derived data issues anymore, I do sometimes run into cases where I need to clear the package cache. And, of course, Xcode's handling of package loading/uploading does slow things down on project open (but I have 66 packages in one project...).

[chrisvasselli]

For example, I just had a successful build, then reset the package cache and rebuilt, and got all these errors, even though the packages look like they're there in the project navigator. 😔 Seems so flaky. Maybe there's just some weird configuration thing I need to fix and it'll all get better. 🤷‍♂️

[chrisvasselli]

FWIW, resetting package again and then building fixed the issue. But it seems like it's always something!

[chrisvasselli]

Haha yeah, there's definitely a certain amount of just learning the weird quirks of our new master. 😆