title: Bringing iOS Frameworks through Carthage in Xcode 12.0
body: <p>I am using Xcode 12.0 and Carthage 0.35.0 and when I do <code>Carthage bootstrap --platform iOS</code> or <code>Carthage update --platform iOS --no-use-binaries</code> on a framework that I have developed I get this error. I did not have this problem in Xcode 11.7.</p>
  <pre><code>
  *** Building scheme &quot;MyFrameworkKit&quot; in MyFrameworkKit.xcodeproj
  Build Failed
      Task failed with exit code 1:
      /usr/bin/xcrun lipo -create /Users/myname/Library/Caches/org.carthage.CarthageKit/DerivedData/12.0_12A7209/MyFrameworkKit/579b0a4ac155ab413da1d73609bf5f24e5ed7cc8/Build/Intermediates.noindex/ArchiveIntermediates/MyFrameworkKit/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/MyFrameworkKit.framework/MyFrameworkKit /Users/myname/Library/Caches/org.carthage.CarthageKit/DerivedData/12.0_12A7209/MyFrameworkKit/579b0a4ac155ab413da1d73609bf5f24e5ed7cc8/Build/Products/Release-iphonesimulator/MyFrameworkKit.framework/MyFrameworkKit -output /Users/myname/Developer/myapp/ios/Carthage/Build/iOS/MyFrameworkKit.framework/MyFrameworkKit
  
  This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/11/tjwvq_yx4mj042kv46mxz1wh0000gn/T/carthage-xcodebuild.gaIzr4.log
  
  </code></pre>
  <p>When I look at the log file mentioned above. I see that the build the was successful. But when I open Xcode and try to build the app I see the message: <code>/Users/myname/Developer/myapp/ios/myapp.xcodeproj Building for iOS Simulator, but the linked framework 'MyFrameworkKit.framework' was built for iOS.</code></p>
  <p>Something must have changed in what type of framework build I can bring into my app from Xcode 11.7 to Xcode 12.0. Do you know what it is that I am missing?</p>
  <p><strong>Update:</strong></p>
  <p>I have been using the workaround suggested in the accepted answer below successfully. Seems like there is a new Carthage release that I yet I have to try. But it does say that it fixes this issue:
  <a href="https://github.com/Carthage/Carthage/releases/tag/0.36.1" rel="nofollow noreferrer">https://github.com/Carthage/Carthage/releases/tag/0.36.1</a></p>