READ THE ENTIRE THING BEFORE YOU MARK THIS AS A DUPLICATE
carthage version:xcodebuild -version:--cache-builds?Cartfile
github "aws/aws-sdk-ios" ~> 2.5
Carthage Output
xcodebuild timeout while trying to read AWSiOSSDKv2.xcodeproj
I'm stuck with the installed version on nevercode's severs. Before I complain to them to upgrade, has this issue been altered/changed since 0.26? If not, then I still have a problem! Ideally we need a command line or environment variable argument to configure this delay! Having to edit and recompile carthage to do this is not a solution!
has this issue been altered/changed since
0.26
The timeout and retry-attempts carthage applies for xcodebuild clean -showBuildSettings … has not changed since 0.26. Check the release notes for future changes, such a change would surely be included there. Important to note: whether the (wall clock) limit gets hit may vary based on Xcode version and the particular checked-out working tree of a repository.
I'm stuck with the installed version on nevercode's severs.… Having to edit and recompile carthage to do this is not a solution!
For my clarification, you’re using nevercode.io and some set of their limitations require not forking carthage?
That should be doable: one strategy would be modifying @raid5’s script to delete unused AWSiOSSDKv2.xcodeproj schemes. Would that work under the set of limitations?
Yes nevercode.io. They have installed Carthage themselves. I mean, I could commit a Carthage binary to our repo, but that would be a ridiculous hack in my opinion. And I don’t even know what I would edit in the Carthage code to fix the problem.
I’ll take a look at that script tomorrow. I’m not sure how I can execute it however, since I’d have to insert the script execution between the Carthage checkout and the build, which happens all at once
This might be fixed with Xcode 9.3. The release notes say:
Fixed a bug which would sometimes cause the -showBuildSettings option to xcodebuild to hang. (33881306)
Is there an option to embed custom script execution as a carthage post checkout, pre build step?
Is there an option to embed custom script execution as a carthage post checkout, pre build step?
No
While the option (with carthage flags) doesn’t exist, the previously mentioned script does a carthage update --no-build¹, then has side-effectual scripting, then carthage build.
Would that work for your purposes?
⑴: Alternatively, carthage bootstrap --no-build.
Maybe... unless both steps incur alot of overhead together (trying to keep the build times down on nevercode).
Either way, it wouldn't hurt to have configurable shell script custom build steps (at various stages of the pipeline). Consider that a feature request :p
@mlfarrell I'm using a custom Carthage script that BuddyBuild runs in place of the default commands. The gist can be found here: https://gist.github.com/raid5/ae5c6787926e7cdd4412ad6bb4456a79
It basically just strips out the schemes I don't need so they aren't built. This dramatically speeds things up.
@raid5 thanks!
I get the same error on the same project file (using Xcode 9.3 beta 4, carthage 0.28.0) and the problem is fixed by deleting Carthage/Checkouts/aws-sdk-ios/AWSAuthSDK (and the xcodeproj file it contains). Fortunately I don't need the contents of that project (3rd party authorization).
For some reason, when carthage tries to open aws-sdk-ios/AWSAuthSDK/AWSAuthSDK.xcodeproj it spawns 30-40 instances of xcodebuild on my tired old 2 core laptop – slowing everything to a crawl – and nothing happens until the timeout message. This happens before any build messages appear (it happens during opening of the project). Something specific in that project is messing with either xcodebuild or carthage.
For some reason, when carthage tries to open aws-sdk-ios/AWSAuthSDK/AWSAuthSDK.xcodeproj it spawns 30-40 instances of xcodebuild on my tired old 2 core laptop – slowing everything to a crawl – and nothing happens until the timeout message. This happens before any build messages appear (it happens during opening of the project). Something specific in that project is messing with either xcodebuild or carthage.
That sounds like it might be fixed in the next release of Carthage by https://github.com/Carthage/Carthage/pull/2343.
@mdiep I just wanted to confirm: Carthage 0.29 fixes the problem I described. Thanks!
Awesome! Thanks for reporting back @mattgallagher.
@mlfarrell How did you find setting up Carthage on Nevercode? I'm about to start this process. Any tips?