carthage update fails about result

[gfontenot]

I believe this is a problem with Carthage. See similar issues Carthage/Carthage#784 and ReactiveCocoa/ReactiveCocoa#2319

[mdiep]

I'm unable to reproduce this. 😕

Can you try running carthage update a few more times to see if you get an error every time or just sometimes?

[gfontenot]

I have seen this (with RAC and Argo), but it's super intermittent. It's working for me now (El Cap GM, official Xcode 7 from the app store), but it wasn't for a few days. I'm not sure what the cause is/was.

[mdiep]

If anyone sees it again, can you post the full output of carthage update?

[github-user32]

Thanks for responding everybody. As luck would have it, I can't reproduce it now either. Yesterday it was happening reliably and since then all I've changed is to quit Xcode and restart it. If I see the problem again I'll post the full output.

[github-user32]

Just managed to reproduce the problem again, although I don't think anything has changed locally that might have caused it. Here's the full output:

carthage update --verbose
*** Fetching ReactiveCocoa
*** Fetching Result
*** Checking out Result at "0.6.0-beta.3"
*** Checking out ReactiveCocoa at "5b18ece9a34597c3dec6ad88d1038d936f7881ba"
Failed to discover shared schemes in project Result.xcodeproj—either the project does not have any shared schemes, or xcodebuild never returned

If you believe this to be a project configuration error, please file an issue with the maintainers at https://github.com/antitypical/Result/issues/new

[gfontenot]

I don't believe this is still an issue. I'm going to close it. @github-user32 if you run into this again, or if it's still an issue, feel free to re-open.

[github-user32]

No problem. I haven’t seen it since, but will let you know if I do. Thanks.

On 26 Nov 2015, at 11:22 AM, Gordon Fontenot [email protected] wrote:

I don't believe this is still an issue. I'm going to close it. @github-user32 https://github.com/github-user32 if you run into this again, or if it's still an issue, feel free to re-open.

—
Reply to this email directly or view it on GitHub #88 (comment).