Apple Mach -O Linker command failed

Question

After updating my POD install, Xcode sprouted a new issue:

Answer 1

There are several cases that cause this issue. At the moment, this question has no any accepted answer and also I found another solution for the same issue, I am posting my answer/experience here.

In you application, go to Target -> Build Settings, then you will find following attributes.

• CLANG_WARN_INFINITE_RECURSION
• CLANG_WARN_SUSPICIOUS_MOVE
• GCC_NO_COMMON_BLOCKS

Set values for those as NO, then clean and build the project.

Answer 2

Remove the local files of WikitudeSDK from target. Xcode is getting confused between the paths of library, which one to chose- pod or local.

Also try reinstalling podfile and remove wikitude from pod file to. IN linker search path settings, in build settings, check the paths mentioned to find the required library.

Lastly install gems before updating pods

Answer 3

First thing you have to do is to delete the files in /Users/Yourname/Library/Developer/Xcode/DerivedData/YourAppName-xxxx and then restart your Xcode. That is no joke!

If you got an error like "duplicate symbol_OBJC_CLASS_$_Pod in:", you should go to TARGETS->Build Phases->Compile Sources and delete extra file.

Answer 4

I experienced the error when overwriting project.

Still encountered the error after:

• Changing the clang settings

• ionic cordova platform remove ios rather than just delete ios platform folder before each new build (and of course add the platform again)

• updating ruby as per instructions: https://forum.ionicframework.com/t/x-code-8-beta-2-apple-mach-o-linker-id-error/71998

Error was solved after changing to a different branch in github but perhaps one of the other troubleshooting methods played a part. Now all branches run on xcode without the Mach -O Linker Error.

Answer 5

Close you project and go to project path and select your project with .xcworkspace instead of .xcodeproj. Reason your existing project doesn't contain any library you linked.

Answer 6

I had faced the same issue. I declared two classes with same name. Therefore it was conflicting with the class name. It worked for me after updation of class name.