Closed dmiluski closed 3 years ago
royjit
commented
3 years ago Looks like carthage archive is not supported in the latest Carthage which is used to create the prebuilt zip file. Raised an issue in Carthage repo to get more information - https://github.com/Carthage/Carthage/issues/3130.
dmiluski
commented
3 years ago Thanks @royjit , I'm following along the in flight Pr for support https://github.com/Carthage/Carthage/pull/3123
Hoping to bring our initial CI build times down soon
lawmicha
commented
3 years ago I can see https://github.com/Carthage/Carthage/pull/3123 is merged in, just checking in to see if ths can be closed or if there are any other actions to take @royjit, and @dmiluski are you unblocked?
dmiluski
commented
3 years ago I can see https://github.com/Carthage/Carthage/pull/3123 is merged in, just checking in to see if ths can be closed or if there are any other actions to take @royjit, and @dmiluski are you unblocked?
@lawmicha i've fully moved over to SwiftPM and unblocked
diegocstn
commented
3 years ago @dmiluski I'll close this for now, but feel free to reopen if you need help with SPM
JeneaVranceanu
commented
3 years ago Had a similar issue with MobileVLCKit while using Carthage 0.36.0 with XCode 13.0 (13A233) on macOS Big Sur 11.6 (20G165).
Fixed the issue by upgrading the Carthage to 0.38.0.
Describe the bug
Unable to install latest 2.2.2, using Carthage 0.37.0.
Invalid archive - Found multiple frameworks with the same unarchiving destinationWhile we use Carthage cache to speed up CI builds (~9 min), each dependency update due to the large size of AWS SDK items can push CI build time well over an hour (90+ min causing failures). I was seeing if this was a known issue? Or if others are seeing this?
For me this is a problem as version 2.2.0 runs into this issue: "Incompatible Swift version - framework was built with 5.3 (swiftlang-1200.0.29.2 clang-1200.0.30.1) and the local version is 5.3.2 (swiftlang-1200.0.45 clang-1200.0.32.28)."
Potentially, could the dynamic frameworks also be uploaded along side of the XCFrameworks with the releases to ease the pain during this transition?
To Reproduce
Steps to reproduce the behavior:
Carthage Error Implementation
Observed Behavior
release xcframework should be installed rather than building schemes
Expected Behavior
xcframework are downloaded rather than seeing this failure and building all schemes (resulting in lengthy builds)
Stack Trace Please provide a stack trace if applicable e.g. a crash is occurring.
Code Snippet
// Cartfile
Cartfile.resolved
Unique Configuration
Areas of the SDK you are using (AWSMobileClient, Cognito, Pinpoint, IoT, etc)?
These were the frameworks our app was using prior to initiating the transition to xcframework.
AWSCognitoIdentityProviderASF AWSCognitoAuth AWSAuthCore AWSCore AWSPinpoint AWSMobileClient
Screenshots If applicable, add screenshots to help explain your problem.
Environment(please complete the following information):
Device Information (please complete the following information):
Additional context Add any other context about the problem here like your specific use case.
Relevant Console Output
N/A