analytics-ios: [4.0.3] [Carthage] Carthage bootstrap fails to resolve package dependencies of Example.xcodeproj
Regression
Failing version: 4.0.3
Last working version: 4.0.2
Carthage version: 0.35.0
Description
When installing analytics-ios version 4.0.3 via carthage bootstrap --platform iOS, the build fails with the following error:
A shell task (/usr/bin/xcrun xcodebuild -project /Users/****/Carthage/Checkouts/analytics-ios/Examples/FullExampleFlow/Analytics\ Example.xcodeproj CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES -list) failed with exit code 74:
xcodebuild: error: Could not resolve package dependencies:
It seems the newly introduced Example project in https://github.com/segmentio/analytics-ios/pull/915 as part of https://github.com/segmentio/analytics-ios/releases/tag/4.0.3 has introduced this issue.
Reverting in Cartfile.resolved to version 4.0.2 won’t reproduce the error.
Logs
A shell task (/usr/bin/xcrun xcodebuild -project /Users/****/Carthage/Checkouts/analytics-ios/Examples/FullExampleFlow/Analytics\ Example.xcodeproj CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES -list) failed with exit code 74:
xcodebuild: error: Could not resolve package dependencies:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (7 by maintainers)
Hi @dchohfi and @jhandguy. I was able to replicate this on our CI and believe we have fixed it. It was related to our example apps using ssh instead of https for SPM.
I’m also curious why Carthage is building our sub-sub projects, but either way this should be fixed with our latest 4.0.4 prerelease.
I’m having a similar issue now with
4.1.0I can confirm the issue is fixed in
4.0.4! 🎉 Thank you for the fast reaction time! 💯@jhandguy @dchohfi I may need some more context in your setup. If I create a new project with a Cartfile.resolved that contains
github "segmentio/analytics-ios" "4.0.3"and executecarthage bootstrap --platform iOSI don’t get any errors. Any other setup information would be helpful so I can assist in tracking down the issue.** Edit ** This was from a fresh project (ie no Carthage cache directory)