IOS development: Xcode reports an error and ios development xcode reports

IOS development: Xcode reports an error and ios development xcode reports

Xcode Error

verify final result code for completed build operationBuild operation failed without specifying any errors. Inpidual build tasks may have failed for unknown reasons.One possible cause is if there are too many (possibly zombie) processes; in this case, rebooting may fix the problem.Some inpidual build task failures (up to 12) may be listed below.

1. Caused by cocoapods

Check that the cocoapods version on the local mac system is the latest 1.4.0

// Delete the 1.4.0 package sudo gem uninstall cocoapods-v 1.4.0 // then install the specified version of cococoapodssudo gem install cococoapods-v 1.3.1 // check the version pod -- version

Then pull the code again, pod update
Compile and run OK!

2. Perform Single-Object Prelink setting causes

Categories in static library

During xcode compilation, all classes in the static library will not be loaded. It will find the symbols used by the main project and then load the used symbols. However, this seemingly beautiful mechanism has a big pitfall, that is, oc classification does not generate symbols. That is to say, for example, you have used a classification method in the project [NSString categoryMethod], the compiler only considers that NSString is needed, but does not know that categoryMethod is a classification method in the static library, so it does not load the classification of the static library.

The current solution is to give the compiler a flag, telling the compiler to load the entire static Library:

1).-all-load. load all. o in all static libraries.
2).-force_load. You can specify which static library to load all. o
3).-ObjC. Load all OC code.
4). Perform Single-Object Prelink.
The first three compilation options are all set in the main project. This option is set in the static library. This sub-project is pre-compiled into a. o file. When a symbol is referenced in the entire static library, the entire. o file is packaged.
It may be because of a bug in the implementation of the Perform Single-Object Prelink. If the file is too large, it will be suspended.