Bitcode error on Xcode10 when doing an export/archive of app with embeded Framework

Question

Created Sep ’18

Replies 1

Boosts 0

Views 1.5k

Participants 2

When building our project for our enterprise we come across this issue with bitcode:

Failed to verify bitcode in TestNetwork.framework/TestNetwork:\nerror: Cannot extract bundle from /var/folders/v2/7k_55wk96ld930ygn2rqh06jc8y98m/T/IDEDistributionOptionThinning.qbT/Payload/TestApp.app/Frameworks/TestNetwork.framework/TestNetwork (i386)

We are manually installing the framework to improve build times. We have the suggested run script in our build phase and this was fine with Xcode 9.4.1.

I added below Run Script also : http://ikennd.ac/blog/2015/02/stripping-unwanted-architectures-from-dynamic-libraries-in-xcode/

APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}" # This script loops through the frameworks embedded in the application and # removes unused architectures. find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK do FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable) FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME" echo "Executable is $FRAMEWORK_EXECUTABLE_PATH" EXTRACTED_ARCHS=() for ARCH in $ARCHS do echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME" lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH" EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH") done echo "Merging extracted architectures: ${ARCHS}" lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}" rm "${EXTRACTED_ARCHS[@]}" echo "Replacing original executable with thinned version" rm "$FRAMEWORK_EXECUTABLE_PATH" mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH" done

This issue occuring only in XCode 10.

Boost

Answer 1

iamteffi OP

Nov ’18

Were you able to figure this out?
I'm having the exact problem. I also tried running the suggested script for removing unsupported architectures but it did nothing. I can confirm that the script was successful.

Update: What I'm trying to do is similar to this radar:
http://www.openradar.me/44073373

With the new build system, exporting assumes that it can be rebuild in bitcode even if its disabled causing the failed verification. This is not the case when using the legacy build system which recognizes bitcode support state on export.

0