title: Xcode 10: Code Signing my App+Framework fails, because of failure signing 3rd party dependency framework (PromiseKit). Works in Xcode 9
body: <p>I have an Xcode 10 - iOS12 swift project that links against My own framework (also Xcode 10 + iOS12). </p>
  
  <p>The app project is referencing my framework project as a sub-project reference.</p>
  
  <p>My Framework project references PromiseKit.framework (a universal framework - fat library), made using the following build script: </p>
  
  <pre><code># Merge Script
  
  # 1
  # Set bash script to exit immediately if any commands fail.
  set -e
  
  # 2
  # Setup some constants for use later on.
  FRAMEWORK_NAME="PromiseKit"
  
  # 3
  # If remnants from a previous build exist, delete them.
  if [ -d "${SRCROOT}/build" ]; then
  rm -rf "${SRCROOT}/build"
  fi
  
  # 4
  # Build the framework for device and for simulator (using
  # all needed architectures).
  xcodebuild -target "${FRAMEWORK_NAME}" -configuration Release -arch arm64 only_active_arch=no defines_module=yes -sdk "iphoneos"
  xcodebuild -target "${FRAMEWORK_NAME}" -configuration Release -arch x86_64 only_active_arch=no defines_module=yes -sdk "iphonesimulator"
  
  # 5
  # Remove .framework file if exists on Desktop from previous run.
  if [ -d "${SRCROOT}/${FRAMEWORK_NAME}.framework" ]; then
  rm -rf "${SRCROOT}/${FRAMEWORK_NAME}.framework"
  fi
  
  # 6
  # Copy the device version of framework to Desktop.
  cp -r "${SRCROOT}/build/Release-iphoneos/${FRAMEWORK_NAME}.framework" "${SRCROOT}/${FRAMEWORK_NAME}.framework"
  
  # 7
  # Replace the framework executable within the framework with
  # a new version created by merging the device and simulator
  # frameworks' executables with lipo.
  lipo -create -output "${SRCROOT}/${FRAMEWORK_NAME}.framework/${FRAMEWORK_NAME}" "${SRCROOT}/build/Release-iphoneos/${FRAMEWORK_NAME}.framework/${FRAMEWORK_NAME}" "${SRCROOT}/build/Release-iphonesimulator/${FRAMEWORK_NAME}.framework/${FRAMEWORK_NAME}"
  
  # 8
  # Copy the Swift module mappings for the simulator into the
  # framework.  The device mappings already exist from step 6.
  cp -r "${SRCROOT}/build/Release-iphonesimulator/${FRAMEWORK_NAME}.framework/Modules/${FRAMEWORK_NAME}.swiftmodule/" "${SRCROOT}/${FRAMEWORK_NAME}.framework/Modules/${FRAMEWORK_NAME}.swiftmodule"
  
  # 9
  # Delete the most recent build.
  if [ -d "${SRCROOT}/build" ]; then
  rm -rf "${SRCROOT}/build"
  fi
  </code></pre>
  
  <p>When I go to archive my Parent App Project using Xcode 10 (And also 9.4.1) with Bitcode ON (that contains My Framework reference, and PromiseKit Fat library), I get the following error on the Signing stage: (Failed to verify bitcode in PromiseKit.framework/PromiseKit: error Cannot extract bundle from /var/folders..../(x86_64)   - which suggests that it's simulator slice related)
  <a href="https://i.stack.imgur.com/SjTgK.png" rel="noreferrer"><img src="https://i.stack.imgur.com/SjTgK.png" alt="enter image description here"></a></p>
  
  <p>If I turn the "Rebuild from Bitcode" option in the Organizer to OFF, then I get a different error: (Code signing "PromiseKit.framework" failed)
  <a href="https://i.stack.imgur.com/CpQYI.png" rel="noreferrer"><img src="https://i.stack.imgur.com/CpQYI.png" alt="enter image description here"></a></p>
  
  <p>However, if I use Xcode 9.4.1 With Bitcode OFF, then it exports and signs fine.  </p>
  
  <p>Why is it trying to individually re-sign sub frameworks, and what can I do to alleviate the issues?   I need the archiving to work normally with Xcode 10, along with any future third party dependencies being added to my framework target.  (This is the first dynamic framework dependency added to my Framework target.  Before I was "baking in" - in-boarding all 3rd parties for ease of development purposes, but PromiseKit is difficult to inboard due to extensive dependencies on Objective-c). </p>
  
  <p>The Xcode Archive log is:</p>
  
  <pre><code> {
          code = 330;
          description = "Failed to resolve linkage dependency PromiseKit x86_64 -&gt; @rpath/libswiftFoundation.dylib: Unknown arch x86_64";
          info =             {
          };
          level = WARN;
      },
              {
          code = 330;
          description = "Failed to resolve linkage dependency PromiseKit x86_64 -&gt; @rpath/libswiftObjectiveC.dylib: Unknown arch x86_64";
          info =             {
          };
          level = WARN;
      },
              {
          code = 0;
          description = "Failed to verify bitcode in PromiseKit.framework/PromiseKit:\nerror: Cannot extract bundle from /var/folders/q5/hm9v_6x53lj0gj02yxqtkmd40000gn/T/IDEDistributionOptionThinning.RJD/Payload/MyAppName.app/Frameworks/PromiseKit.framework/PromiseKit (x86_64)\n\n";
          info =             {
          };
          level = ERROR;
          type = "malformed-payload";
      }
  );
  </code></pre>
  
  <p>Some other solutions I tried was using a Project Reference to PromiseKit, instead of a Framework reference, however this doesn't work - in that I still need a framework reference from my main project, because I will get "library not loaded" error at runtime, if running without a FW reference. Same issue occurs when archiving while using a project reference.  </p>