Carthage update fails to build framework about pusher-websocket-swift HOT 6 CLOSED

I had the same issue and it took a while to resolve it. I still do not know what is causing it exactly. What I ended up doing was updating cocoapods to 1.0.0.beta.6 with. Then I tried to update and it failed as before. After that I went into the Carthage checkout and did pod install. See if this works for you:

sudo gem install cocoapods -v 1.0.0.beta.6
carthage checkout pusher-websocket-swift
cd Carthage/Checkouts/pusher-websocket-swift
pod install
cd ../../..
carthage update --platform ios pusher-websocket-swift

I do not like that we have to have correct versions of cocoapods and manage those. That is not "Carthage compatible" in my mind

from pusher-websocket-swift.

I ended up installing via Cocoapods anyway as I was only developing a POC and was limited on time... Just quickly opened the issue as I spotted it..

Yeah you're right though.. Having to have Cocoapods as a dependency for using Carthage isn't right... My guess is that the pods should be checked in with the project so that the framework can be compiled by Carthage without any issues.

Sent from my iPhone

On 24 Apr 2016, at 22:08, Keilan Jackson [email protected] wrote:

I had the same issue and it took a while to resolve it. I still do not know what is causing it exactly. What I ended up doing was updating cocoapods to 1.0.0.beta.6 with. Then I tried to update and it failed as before. After that I went into the Carthage checkout and did pod install. See if this works for you:

sudo gem install cocoapods -v 1.0.0.beta.6
carthage checkout pusher-websocket-swift
cd Carthage/Checkouts/pusher-websocket-swift
pod install
cd ../../..
carthage update --platform ios pusher-websocket-swift
I do not like that we have to have correct versions of cocoapods and manage those. That is not "Carthage compatible" in my mind

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

from pusher-websocket-swift.

Sorry for not jumping in on this one sooner. You're right that the pods should really be included. The next release removes the pod dependencies and so that should make things a lot easier whether you're using Carthage or Cocoapods.

You can follow along the progress of the next release here: #34

I'll leave this open for now

from pusher-websocket-swift.

Great stuff :)

Liam
Sent from my iPhone

On 25 Apr 2016, at 09:33, Hamilton Chapman [email protected] wrote:

Sorry for not jumping in on this one sooner. You're right that the pods should really be included. The next release removes the pod dependencies and so that should make things a lot easier whether you're using Carthage or Cocoapods.

You can follow along the progress of the next release here: #34

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

from pusher-websocket-swift.

Adding the 1.0.0 release milestone as this will be fixed there

from pusher-websocket-swift.

1.0.0 has just been pushed

from pusher-websocket-swift.