We have a static library we've been distributing for some time, and now want to distribute it as a framework. The static library is built to contain both phone and simulator slices by performing two xcodebuild commands and lipo'ing the results together. This has been working fine.
But when I initially attempted to apply the same approach to a framework, the App Store validation process griped that the resulting product wasn't built for full bitcode. Having looked into it, people online are saying I need to use archive instead of build for the device slice. It results in an xcodebuild command like this:
xcodebuild archive -target OurProduct -scheme OurProduct -archivePath ./Archive/OurProduct.xcarchive
Now at this point I appear to have a valid xcarchive. Then I'm running:
xcodebuild -exportArchive -archivePath "./Archive/OurProduct.xcarchive" -exportPath "./Archive/OurProduct.framework" -exportOptionsPlist "./exportOptions.plist"
But I get the error:
error: exportArchive: exportOptionsPlist error for key 'method': expected one of {}, but found app-store
"app-store" is the value of key "method" in my export options plist file. I need some help trying to understand what could be the problem here, or if there's a more proper way to do this.
