xcode 7.1 swift framework app builds but not archiving

Question

I have created a sample Framework in Swift, xcode 7.1. The framework is then built for Profiling, released version. Released framework then added(embedded) to an iOS test app.

The app builds fine, but when trying to archive it. An error occurs, stating "bitcode bundle could not be generated because '.../Test/FW.framework/FW' was built without full bitcode. All frameworks and dylibs for bitcode must be generated from Xcode Archive or Install build for architecture arm64"

The Framework and app projects are on default settings, Bitcode enabled for both.

To make sure Framework have bitcode, this command on Framework

"otool -l FW.framework/FW | grep __LLVM"

yields

segname __LLVM

What am I missing? I have included both projects here, you can download them and try archiving.

seems the bitcode formats don't match. was the framework exported via archiving it? — Daij-Djan
– Daij-Djan, Commented Nov 7, 2015 at 9:19
No, just built it for Profiling, then found the FW.framework in "Release-iphoneos" along with a separate file "FW.framework.dSYM". — fullstackduck
– fullstackduck, Commented Nov 7, 2015 at 9:21
How can I export it via archiving? When I archive the framework, it says build succeeded and nothing happens. Do I need to look for archived framework output file — fullstackduck
– fullstackduck, Commented Nov 7, 2015 at 9:22
maybe building for archiving works too but to allow it to be put into an archive, set the build setting 'skip install to NO' — Daij-Djan
– Daij-Djan, Commented Nov 7, 2015 at 9:23
That did the trick, thanks! I was going insane over this. Please add the steps as answer, I will accept it. ( 'skip install to NO' on framework project, then archive, export with save built product and that Framework output file works with bitcode enabled) — fullstackduck
– fullstackduck, Commented Nov 7, 2015 at 9:37

Daij-Djan · Accepted Answer · 2015-11-07 09:42:03Z

37

xcode requires that bitcode for all embedded frameworks is generated during archiving.

Copying the release build of framework/dylib isn't enough

do
archive the framework and THEN use the archived version of the framework from then on.

to get xcode to archive a framework (normally it only archives apps), set the build setting 'skip install' to NO for the framework target!

answered Nov 7, 2015 at 9:42

Daij-Djan

50.2k17 gold badges116 silver badges138 bronze badges

Sign up to request clarification or add additional context in comments.

12 Comments

saltwat5r Over a year ago

It works, but not enough... Project now builds successfully with framework, but while uploading to iTunesConnect I receive an error...

saltwat5r Over a year ago

` An error occurred during validation The archive did not contain <DVTFilePath:0x7f9bea07f750:'/Users/me/Library/Developer/Xcode/Archives/2015-12-16/Project_name 16-12-15 16.16.xcarchive/BCSymbolMaps/D1F093C6-C59A-3761-8C62-8D74B8629FB23.bcsymbolmap'> as expected.`

Daij-Djan Over a year ago

K. I'm lost. How do you produce it? Have you checked if it has module map at all?

saltwat5r Over a year ago

The error occurred while uploading archive to iTunesConnect... Additional error info screenshot What do You mean with "checked if it has module map at all" ?

ort11 Over a year ago

Thanks, setting the SKIP INSTALL to NO worked since the framework has to have to BITCODE to NO for a store upload. Then can export the archive to framework and then copy / use that for the app.

|

hbk · Accepted Answer · 2017-08-11 09:19:33Z

36

You can make the following if you can build the framework (for example if you use your own framework)

This will allow your framework to provide the required bitcode.

Another alternative option may be applicable if you dont have watchOS and Apple TV (according to docs)

For iOS apps, bitcode is the default, but optional. If you provide bitcode, all apps and frameworks in the app bundle need to include bitcode. For watchOS and tvOS apps, bitcode is required.

this option require to set ENABLE_BITCODE for every target in buildSetting to NO, but as expected this forbid to use bitcode functionality.

More about bitcode here