No shared framework schemes for iOS platform about plcrashreporter HOT 7 CLOSED

Hi @mtfourregp, thank you for reporting this. I've reproduced the issue with a test app and currently trying to find a root cause. Will keep you updated on the progress.

from plcrashreporter.

Thanks very much @roland-chernov-akvelon for the quick reply. Your help is greatly appreciated. Let me know if I can do anything to assist.

from plcrashreporter.

Hey @mtfourregp,

not sure where you read that PLCR supports Carthage. We're not claiming it does and I don't remember claiming it. Any chance you can point me to where you read this? I'd like to avoid any miscommunication about this.

Best,
Benjamin

from plcrashreporter.

Hi @ElektrojungeMS ,

I think the confusion here came about as I was browsing through some issues on GitHub regarding PLCrashReporter/Carthage compatibility when a user linked to the following pull request:

#12 (comment)

I believe I then falsely attributed your fork to solving a Carthage compatibility issue where in fact your fork solves a separate issue which coincidentally also resolved a Carthage compatibility issue. So in fact you haven't claimed to support Carthage. I have drawn an incorrect conclusion from my experience reading through a number of pull requests. My apologies for the confusion and miscommunication.

-Michael

from plcrashreporter.

I'd like to share some details that I found after investigation of this issue:

• PLCrashReporter has CrashReporter-iOS scheme which depends on 2 schemes: CrashReporter-iOS-Device and CrashReporter-iOS-Simulator. I looked through device and simulator schemes: they differ only by used architectures.
• CrashReporter-iOS.xcscheme wasn't committed to the repository, that's why Carthage can't find it.
• Xcode generates CrashReporter-iOS.xcscheme automatically (diff). But after committing the scheme file, build still fails:

  $ carthage build --no-skip-current --platform iOS --verbose
  <...>
  Build system information
  error: Multiple commands produce '<SetMode /Users/roland/Library/Developer/Xcode/DerivedData/CrashReporter-fbzxvzkmupquzfbtzowsntsiwdpg/Build/Intermediates.noindex/ArchiveIntermediates/CrashReporter-iOS/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/libCrashReporter-iphoneos.a>':
  1) Target 'CrashReporter-iOS-Simulator' (project 'CrashReporter'): SetMode u+w,go-w,a+rX /Users/roland/Library/Developer/Xcode/DerivedData/CrashReporter-fbzxvzkmupquzfbtzowsntsiwdpg/Build/Intermediates.noindex/ArchiveIntermediates/CrashReporter-iOS/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/libCrashReporter-iphoneos.a
  2) Target 'CrashReporter-iOS-Device' (project 'CrashReporter'): SetMode u+w,go-w,a+rX /Users/roland/Library/Developer/Xcode/DerivedData/CrashReporter-fbzxvzkmupquzfbtzowsntsiwdpg/Build/Intermediates.noindex/ArchiveIntermediates/CrashReporter-iOS/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/libCrashReporter-iphoneos.a
  
  ** ARCHIVE FAILED **
  
  Build Failed
      Task failed with exit code 65:
      /usr/bin/xcrun xcodebuild -project /Users/roland/Source_code/PLCrashReporter/CrashReporter.xcodeproj -scheme CrashReporter-iOS -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/x5/dplx6vds5370q8p22qw186zr0000gp/T/PLCrashReporter SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/roland/Source_code/PLCrashReporter)
  
  This usually indicates that project itself failed to compile.
  

from plcrashreporter.

Hey @mtfourregp,

We're currently not investing to add Carthage support. Maybe @ jonathanwong's fork https://github.com/jonathanwong/plcrashreporter works for you?
If you want to contribute a PR, we're also happy to accept that.

Cheers!
Ben

from plcrashreporter.

Thank you @roland-chernov-akvelon for the information. I can see why there might be issues building with that scheme setup. I'll have to dig a bit more to find out where the root of the failure is. As of now it still seems unclear to me. I appreciate you spending the time to check it out.

@ElektrojungeMS I understand that you all won't want to spend time on this issue. Thanks for looking anyway. Unfortunately the fork you linked suffers from the same problem, so it won't be of any help. I'll be looking around for a solution to this. If there is a backward compatible option which would make sense in this repository, I will open a pull request to address it.

-Michael

from plcrashreporter.