iOS Common error Analysis resolution (always updated) you are worth collecting-comprehensive stickers

-From the collection summary of a lot of common mistakes

1:clang failed with exit code 254

One: Detects if there is a NSLog in the code that prints a value that returns void.

2:verify exit code of build task with internal identifier ' Copypngfile 123.png '

One: The wrong png, use Photoshop to re-convert once, if Photoshop cannot open, change the suffix to jpg try. When converting, use: Save the format format used by the Web or device to convert to PNG-24 the size of the picture is more appropriate.

3:

One: Determine if there is a custom class file in the static library, and if not, this error will occur, which is why the new static library contains a default class.

4: _objc_class_$_uimainkpixml ", referenced from:

1: Detects if the class file has specified project Target

2: Detects if the class file Compile Source in Bulid phases contains this class file

After the above two steps are checked, if you compile the also reported error, try to completely turn off Xcode to compile again.

5:for Architecture armv7s

Following excerpt from: http://stackoverflow.com/questions/12570116/what-is-the-difference-between-arm7-and-arm7s

Yes right about armv7s was about the IPhone 5. Here some summary Info I found on the Web:

• ARMv6 ISA (used by the ARM11 core in the iphone 2G and iphone 3G)
• ARMV7 (used by modern ARM cores, iphone 3GS, iphone 4 and 4S)
• armv7s (new A6 SoC for IPhone 5).

Note: The error meaning indicates that the specified framework does not support support for armv7s and does not support iphone 5 with A6 processors.

If the compilation is still in the project of the framework or the static library, the following settings may be the result, set to No

6:local declaration of ' hides instance variable

1: The private variable has the same name as the property variable

7:instance variable "accessed in class method

1: The static method cannot use the property variable to the class, otherwise the above error is reported

8:Ld:symbol (s) not found for architecture i386

1: Inside the meaning said: "_stroyboard" This attribute in the target class is not declared at all!

Let's just declare it, huh? Note: XCode4.5 is declared by default, but only for custom classes, not the system class. So, be careful.

1. @synthesize Storyboard;

9:performselector may cause a leak because it selector is unknown

Resolve the resulting compiler warning with the following code

2. #pragma clang diagnostic push
4. #pragma clang diagnostic ignored "-warc-performselector-leaks"
6. [Self performselector:nextview];
8. #pragma clang diagnostic pop

Source: (http://www.ooso.net/archives/620)

10:unable to open executable

1: Detect if there are two or more similar files in the same static library or project

2: Remove the app from the emulator, remove the Deriveddata folder and restart Xcode.

11:property ' s synthesized getter follows COCOA naming convention for returning ' owned ' objects

Do not declare the variable name in the header file to start with new copy

Reference: http://kongbei888.blog.163.com/blog/static/24326613201261902510652/

12:ld:file not found:

1: Point to Static library not found

: _utf8_counttrailbytes

Add Library Libicucore.dylib

15:stray "@" in program

The compiler version used by the project is too low. Modify the compiler version to the latest version, such as:

Reference: Http://stackoverflow.com/questions/12821938/stray-in-program-with-nsdictionary-definition

16. Troubleshooting Errors when you debug your ipad Air device on a real machine: architecture not supported approach1. Delete the arm64 of architectures--> Valid architectures in Build Settings, leaving only armv7, armv7s

2. Ditto, change Architectures-->architectures to $ (arhs_standard) armv7,armv7s

3. Change build Active Architecture only to No

4. Compile to

17. Compile-time appearance: not supported ARM architecture

Workaround: Add-d__arm_arch_5tej__ when the./configure

Another article:android common error analysis

This article has been updated to participate in the update of this article by encouraging you to respond to common error that you know about ^_^