Apple Mach -O Linker (Id) Error?

前端 未结 12 532
借酒劲吻你
借酒劲吻你 2020-12-29 06:49

I am trying to build this xcode workspace which was built from Unity. And after modifying the project a little bit when I getting to the very end of building the project (li

相关标签:
12条回答
  • 2020-12-29 07:08

    How I resolved this issue:

    1. I exit Xcode then opened my project's .xcworkspace again.

    2. While Xcode was starting...i saw warnings...xcode is smarter enough and ask you switch to recommended settings...Tap it and let him do the changes. (Read warning seriously and with positive mind and then you will resolve it)

    0 讨论(0)
  • 2020-12-29 07:16

    If building on mac for ios in unity, make sure that in the build settings you disable "Metal Editor Support" under other settings for the ios platform.

    0 讨论(0)
  • 2020-12-29 07:16

    I used xcode 9.3 and I got this same error. But with 9.2 it works. The error may happen because of incompatibilities between the artifacts produced by the two xcodes. The project that threw the error included a framework built with xcode 9.2

    0 讨论(0)
  • 2020-12-29 07:18

    This issue was connected to "Link Binary With Libraries". I've renamed the target, and there were two .framework files for the Pods. Thus, after removing the outdated one - the issue was solved.

    0 讨论(0)
  • 2020-12-29 07:18

    If you just installed/ uninstalled a pod you might want to look at this. Here's what worked for me:

    1. First make sure you are opening the .xcworkspace file not the .xcodeproj. But this is probable not what's causing the issue.

    2. Delete the pod that was recently just installed.

    3. In the project directory on Xcode, open the frameworks folder and if the pod which was just removed is still listed there as one recentlyremovedpod.framework, delete it from there also. This step is what made my project compile eventually.

    0 讨论(0)
  • 2020-12-29 07:19

    This problem has different solutions , one of them is to set Enable Bitcode to No . ( I don't know why by default it is Yes )

    This problem is a ghost like problem . Clearing Cache , Restarting Xcode , Simulator and MAC ,Ensuring proper linking of Frameworks ,Changing app Architecture or , Sometimes just doing nothing can solve this problem .

    0 讨论(0)
提交回复
热议问题