bugsnag-cocoa: I can't install Bugsnag on Carthage + Xcode11

Description

Bugsnag won’t install using XCode 11 + Carthage

Environment

Library versions:

Bugsnag version (from your Podfile, Podfile.lock, or elsewhere): 5.22.7
Carthage version (if any): 0.33
iOS/tvOS/macOS version(s): MacOSX 10.15 Catalina

Example code snippet

carthage update bugsnag-cocoa --no-use-binaries --cache-builds --platform iOS

Result

(1 failure)
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -workspace /Users/marcelosalloum/Workspace/persona-ios/Carthage/Checkouts/bugsnag-cocoa/OSX.xcworkspace -scheme Bugsnag -configuration Release -derivedDataPath /Users/marcelosalloum/Library/Caches/org.carthage.CarthageKit/DerivedData/11.0_11A420a/bugsnag-cocoa/v5.22.7 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/g_/x9df0hls2k51twkgxtx68k9w0000gn/T/bugsnag-cocoa SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/marcelosalloum/Workspace/persona-ios/Carthage/Checkouts/bugsnag-cocoa)

This usually indicates that project itself failed to compile.

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 17 (4 by maintainers)

Commits related to this issue

build: Consolidate projects into one Fixes an issue mentioned in #418 where the Bugsnag project would build multiple times, once for each architecture. — committed to bugsnag/bugsnag-cocoa by kattrali 5 years ago
build: Consolidate projects into one Fixes an issue mentioned in #418 where the Bugsnag project would build multiple times, once for each architecture. — committed to bugsnag/bugsnag-cocoa by kattrali 5 years ago

Most upvoted comments

Thanks for checking, @marcelosalloum.

I’ve made some updates to your changes so we no longer build all three frameworks when carthage --platform XXX is used and opened a PR against your branch (#419).

Thanks for this, @Sidetalker. The changeset resolves the issue, but due to the way that some people integrate (vendoring/submoduling bugsnag-cocoa and adding the project to theirs), I can’t change the target name or project locations without first seeing just how breaking it will be and making the appropriate upgrade guide or major version. I’ve made an near-term fix in #423 to get Carthage working again, though it does still build three times. I’ve also updated the automated tests to ensure Carthage builds succeed on every platform so this doesn’t happen again.

I am working on a slightly different approach in the branch kattrali/fix-carthage-building-multiple-times which instead removes the different projects in favor of one in the root of the repository, which resolves the build repeat issue as well as reducing risk of Carthage builds for the different platforms being different from counterparts using other packaging systems.

kattrali on Oct 10, 2019

Released in v5.22.9

mattdyoung on Oct 16, 2019

I’m new on Carthage, so I’m not sure what may be the issue there.

Try removing ~/Library/Caches/org.carthage.CarthageKit/? Sometimes the cache is stale.

kattrali on Oct 8, 2019

By the way: I can install v5.22.6 just fine.

EmDee on Oct 8, 2019

Hi @marcelosalloum @Sidetalker

Thanks, we’ll take a look at what’s required for the proper fix for this.

mattdyoung on Oct 7, 2019

For the time being, I’ve just reverted the commit that broke Carthage. No PR because this is not a real “fix” - https://github.com/Sidetalker/bugsnag-cocoa

Sidetalker on Oct 4, 2019