openid / openid/AppAuth-iOS

Pod GTMAppAuth and AppAuth together causes Archive issues: Multiple commands produce....

Open
#463 5 comments 0 reactions 1 assignee View on GitHub

@petea is already working on this.

Since May 29, 2020.

Dominant language
Objective-C
Stars
2k
Forks
867
Avg merge
4d 48m
Merged PRs (30d)
1

Description

I have the following in my Podfile

target 'Claritist' do
  use_frameworks!
  # pod 'KMNavigationBarTransition'
  pod 'FontAwesome.swift'
  pod 'Eureka'
  pod 'PDTSimpleCalendar', '~> 0.9.1'
  pod 'SimpleImageViewer', :git => 'https://github.com/aFrogleap/SimpleImageViewer.git'
  pod 'SwiftDate'
  pod 'AFDateHelper'
  pod 'BadgeSwift', '~> 7.0'
  pod 'CallbackURLKit'
  pod 'GoogleAPIClientForREST/Gmail'
  pod 'GTMAppAuth'
  pod 'AppAuth'
  pod 'FTLinearActivityIndicator'
  pod 'Down'
  pod "MarkdownKit"
end

Build and run in simulator, everything is fine, until I try to do an "Archive", then I get the following error:

Multiple commands produce '/Users/supermonk/Library/Developer/Xcode/DerivedData/Claritist-hfetowswkdbjyygxvccgxsiufuhk/Build/Intermediates.noindex/ArchiveIntermediates/Claritist/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AppAuth.framework':
1) Target 'AppAuth-Core' has create directory command with output '/Users/supermonk/Library/Developer/Xcode/DerivedData/Claritist-hfetowswkdbjyygxvccgxsiufuhk/Build/Intermediates.noindex/ArchiveIntermediates/Claritist/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AppAuth.framework'
2) Target 'AppAuth' has create directory command with output '/Users/supermonk/Library/Developer/Xcode/DerivedData/Claritist-hfetowswkdbjyygxvccgxsiufuhk/Build/Intermediates.noindex/ArchiveIntermediates/Claritist/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AppAuth.framework'

The AppAuth-Core comes from GTMAppAuth, and I am not sure which library is the one I should be filing bug against!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.