更新为Xcode 10.1，以下解决方案为我工作:

你只需要从嵌入式二进制文件中删除框架，并将其添加到链接框架和库中。

参考下面的截图;

即使在添加脚本和更新框架几次之后，我也遇到了同样的问题。

确保在xCode中脚本被添加在嵌入之后的末尾。我想我不小心在嵌入框架之前移动了脚本。

注意:我有xCode 9.1

我从构建设置-有效架构-发布中删除了i386和x64_86架构，一切都工作得很好。

现在唯一的问题是您不能为了测试目的在模拟器上运行RELEASE版本。但是，如果你想的话，你可以很容易地把它们加回来。

I will add my 2 cents here (in a less scary way :-). I have encountered quite a number of fat libraries from Vendors that (for some reason) do not work the normal way by adding them to the Frameworks directory as documented by Apple. The only way we have been able to make them work is by pulling the .framekwork right into the project directory and linking the Embedded Frameworks and Link Binary with Libraries manually in Build Settings. This seem to have worked without any issues, however, as with any fat library they come with the extraneous Simulator Architectures i386 and x86_64 along with the arm architectures.

检查fat库上的架构的一个快速方法是

$ cd 'Project_dir/Project'
$ lipo -info 'YourLibrary.framework/YourLibExec`

哪个应该吐出这样的输出

Architectures in the fat file: YourLibrary.framework/YourLibExec are: i386 x86_64 armv7 arm64

这证实了你需要在iTunesConnect存档上传之前从你的框架中“修剪脂肪”(即i386和x86_64)，这是不允许这些架构的(因为它们不支持iOS)。

现在，这里所有的答案(或者至少部分答案)提供了这些出色的运行脚本，我确信它们工作得非常好，但前提是你的框架位于Frameworks目录下。现在，除非您是一个shell脚本爱好者，否则这些没有修改的脚本将不适用于我上面解释的场景。然而，有一种非常简单的方法可以从框架中摆脱i386和x86_64架构。

在项目目录中打开终端。 将目录直接更改为. framework，例如 cd YourProjectDir /志愿者项目/ YourLibrary.framework 运行如下所示的命令-

$ mv YourLibrary YourLibrary_all_archs
$ lipo -remove x86_64 YourLibrary_all_archs -o YourLibrary_some_archs
$ lipo -remove i386 YourLibrary_some_archs -o YourLibrary
$ rm YourLibrary_all_archs YourLibrary_some_archs

这里有几件事要注意-脂肪-去除必须做一次每个架构去除。Lipo不会修改输入文件，它只生成一个文件，因此您必须为x86_64和i386运行一次Lipo -remove。上面的命令只是通过首先重命名可执行文件，然后最终删除所需的arch，然后清理剩下的文件来实现这一点。就这样，你现在应该看到一个绿色的复选标记在应用加载存档上传到iTunesConnect。

Things to keep in mind : The above steps should only be done while production build, since the .framework will be stripped off the simulator architectures, builds on simulators will stop working (which is expected). In development environment, there should be no need to strip the architectures off of the .framework file since you want to be able to test on both Simulator and a physical device. If your fat library resides in the Frameworks folder in the project then please look at the accepted answer.

如果您正在使用Carthage，请确保您的嵌入框架构建步骤在Carthage复制框架之前

在一些不寻常的情况下(例如:Lottie-iOS框架):

你可以像往常一样在“链接库”中找到它。 然而，你还必须显式地在“嵌入框架”中添加它(即使这看起来毫无意义，因为当你只在“嵌入框架”中添加它时，它会完美地工作)， 然后把它放到复制框架中 确保copy-frameworks在“Embed Frameworks”后面

问题是Buy框架包含模拟器(x86_64)和实际设备(ARM)的构建。

当然，你不允许向App Store提交不受支持的架构的二进制文件，所以解决方案是在提交之前“手动”从最终二进制文件中删除不需要的架构。

Daniel Kennett提出了一个很好的解决方案，并提供了这个脚本添加到构建阶段:

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

我用过，效果很好。

编辑:请务必查看Varrry发布的修改后的脚本，因为这个脚本有一些小问题。