Bolts causing CI failure

[dplewis]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and the Parse ObjC SDK.

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]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

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]

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 dplewis#10

[mtrezza]

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

[dplewis]

Looks like SPM is working but CI using Carthage breaks.

#1758

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