parse-community / Parse-SDK-iOS-OSX

The Apple SDK for Parse Platform (iOS, macOS, watchOS, tvOS)
https://parseplatform.org
Other
2.81k stars 871 forks source link

Bolts causing CI failure #1759

Closed dplewis closed 1 year ago

dplewis commented 1 year ago

New Issue Checklist

Issue Description

Build Failed
    Task failed with exit code 65:
    /usr/bin/xcrun xcodebuild -project /Users/runner/work/Parse-SDK-iOS-OSX/Parse-SDK-iOS-OSX/Carthage/Checkouts/Bolts-ObjC/Bolts.xcodeproj -scheme Bolts-iOS-Dynamic -configuration Release -derivedDataPath /Users/runner/Library/Caches/org.carthage.CarthageKit/DerivedData/14.3.1_14E300c/Bolts-ObjC/1.9.1 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive VALIDATE_WORKSPACE=NO -archivePath /var/folders/r_/vbvvglrx3lvds6dp_mbyq3_c0000gn/T/Bolts-ObjC SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/runner/work/Parse-SDK-iOS-OSX/Parse-SDK-iOS-OSX/Carthage/Checkouts/Bolts-ObjC)
parse-github-assistant[bot] commented 1 year ago

Thanks for opening this issue!

mtrezza commented 1 year ago

Interesting that the CI passed for the PR branch but failed for the master branch. Could that be because of the Cache Carthage step? It could have cached something that is not generated anymore due to the PR, that's why it may still have passed, but then failed on the master branch where there was no cache. If so, then we should probably remove the Cache Carthage step from the CI to avoid that in the future.

dplewis commented 1 year ago

Interesting that the CI passed for the PR branch

Thats old news

Could that be because of the Cache Carthage step?

I already tried that https://github.com/dplewis/Parse-SDK-iOS-OSX/pull/10

mtrezza commented 1 year ago

Does this affect the SDK when adding it via SPM or only the CI?

dplewis commented 1 year ago

Looks like SPM is working but CI using Carthage breaks.

https://github.com/parse-community/Parse-SDK-iOS-OSX/pull/1758

I’ll reopen it after some local trial and error testing