Carthage update fails on ObjC SDK, due to git vs https schemes.

[CiraciNicolo]

I'm trying to install this SDK for the ParseFacebookUtils, but I encounter the same error. The shell output is this:

The build works if I remove the Facebook dependencies.

[thertzelle]

I'm getting the exact same message on my machine, first time i've tried to use carthage to install this framework.

I can confirm that I'm running Carthage 0.17.2

Updated:

I found out that my company apparently is blocking git:// scheme, which is unfortunate, i'l have to get that looked into. I found that Facebook-SDK has many different protocols for their dependancies being checked out git:// https:// and ssh:// -- Seems like it could be standardized.

Anyway, running the following command allowed me to build successfully:

git config --global url."https://".insteadOf git://

[thertzelle]

I submitted this pull request to the master repository in attempts to get the issue resolved:

facebook/facebook-ios-sdk#839

[nlutsenko]

Blocked git:// scheme - that sounds very weird!
It is a great idea to use https instead of git for submodules, we should definitely do that instead to avoid issues like this.

Going to ping some folks internally, but overall, that PR should go out together with the next release of ObjC SDK (likely in about 3 weeks).

In the meantime - I would suggest trying to get git:// scheme unblocked for you or use a different internet connection.

[nlutsenko]

Quick update here... Looks like ObjC SDK 4.15.1 got released, but the schemes got overriden again from https back to git 😭
Going to take a look at the ObjC SDK and make sure that it's back in the proper state, so you guys can checkout via Carthage over https.

[nlutsenko]

This should be almost fixed with 4.16 (my patch for FBTweaks there didn't make the cut 😢 ).
The core installation part should be fixed though, so I would recommend everyone to give it a try.

[nlutsenko]

ObjC SDK 4.17 was finally released and it includes the fix for https scheme.
Sorry folks it took us a while to fully and finally fix this.
It is going to be available in the next SDK version.