XCode 8.3归档错误:链接器命令失败,退出代码为1

XCode 8.3归档错误:链接器命令失败,退出代码为1

问题描述:

我只是在从XCode 8.2升级到XCode 8.3之后才开始出现此错误,而仅在进行存档构建时(调试构建工作正常)。

I started getting this error only after upgrading from XCode 8.2 to XCode 8.3, and only when making an archive build (debug builds work fine).

当我通过XCode进行存档时,我得到的唯一消息是链接器命令失败,退出代码为1(使用-v查看调用)。

When I do the archive via XCode, the only message I get is "Linker command failed with exit code 1 (use -v to see invocation).

我使用命令行构建 xcodebuild -scheme MyProduct

当我以这种方式构建时,我发现了许多问题(再次,仅在进行存档时):

When I built this way, I found a number of issues (again, only when doing Archive):


  • 我必须添加 import UIKit 几乎所有swift文件。

  • 所有pod都有问题

  • 从app-Bridging-Header.h删除所有内容

  • 将一些内容添加回app-Bridging-Header.h

  • I had to add import UIKit to practically every swift file.
  • all the pods had issues
  • remove everything from app-Bridging-Header.h
  • add a few things back into app-Bridging-Header.h

我当前的问题是AWS pod,使用版本2.5.3

My current issue is with the AWS pod, using version 2.5.3

所以我的app-Bridging-Header.h有 #import< AWSS3 / AWSS3.h>

So my app-Bridging-Header.h has #import <AWSS3/AWSS3.h>

以下是命令行构建中的错误:

Here is the error from the command line build:

error: 'AWSS3/AWSS3.h' file not found with <angled> include; use "quotes" instead
#import <AWSS3/AWSS3.h>
        ^

之后错误日志继续。我也尝试了在导入中切换到AWSS3 / AWSS3.h的疯狂建议......这也没有用。

The error log continues after that. I also tried the crazy suggestion of switch in the import to "AWSS3/AWSS3.h"...that didn't work either.

关于什么事情的任何想法在?

Any ideas on what is going on?

更多信息

这似乎是一个问题我的豆荚。我构建了一个新的解决方案,导入了我的pod的一个子集和所有内置的东西。然后,当我更新完整的pod列表时,它就崩溃了。

This really appears to be an issue with one of my pods. I built a new solution, imported a subset of my pods and everything built. Then when I updated with the full list of pods it broke.

最后我才弄明白这是一个pod问题...只需弄清楚它是哪一个。

At long last I was able to figure out this was a pod issue...just had to figure out which one it was.

我创建了一个全新的项目并开始逐个添加我的pod(实际上,3个3 ...一个接一个地花了太长时间。)

I created a brand new project and started adding my pods in one by one (actually, 3 by 3...one by one would have taken too long).

结论:localytics 4.3.1在某个地方有一个错误。我降级到4.3.0,问题就消失了。

Conclusion: localytics 4.3.1 has a bug in it somewhere. I downgraded to 4.3.0 and the problem went away.