I know that this is a duplicate question. I followed the answers posted in the other similar Stack Overflow questions and I also tried answers posted on other websites. But, I still get the below error. So, please help me to get rid of this error.
Asked
Active
Viewed 502 times
0
-
1http://stackoverflow.com/questions/6429494/undefined-symbols-for-architecture-armv7 Check this – Pramod Tapaniya Feb 02 '16 at 08:23
-
Please post the text, not a screenshot. – trojanfoe Feb 02 '16 at 08:34
-
@PramodTapaniya I followed up already but I still get error. – Inuyasha Feb 02 '16 at 08:39
-
Import uikit framework in your project and write import statement in .h file. – Pramod Tapaniya Feb 02 '16 at 08:41
2 Answers
2
Those are all system classes. You are somehow failing to link against the UIKit.framework.
In order to solve these kinds of problems yourself, look at the text after _OBJC_CLASS_$_ and
- If that is one of the classes in your source tree, you have failed to add the implementation file to an Xcode target.
- If it's not then Google it to find which library/framework it belongs to, and that is the library/framework you are failing to link against.
trojanfoe
- 120,358
- 21
- 212
- 242
-
Thank you save my day. I just link UIKit.framework again and it work fine. – Inuyasha Feb 02 '16 at 08:47
0
The issue is with the file which you have imported. Can you please check whether you have imported .h file or .m file in your class?
This error is shown mainly in two situations :-
- When you import .m file of some other class in your current class instead of .h file
- When you add .h file to your target's Compile sources instead of .m file
Arun
- 1,391
- 1
- 10
- 29
-
-
@trojanfoe Actually I have faced the same issue when I have done the above mistakes. In my case also all the frameworks where added to the target. The issue was I imported .m instead of .h – Arun Feb 02 '16 at 08:43
-
Well it depends on what classes are missing, as explained in my answer. – trojanfoe Feb 02 '16 at 08:44
-
my Xcode not find arm7 and arm6 how solve this on bug for Xcode e – Ramani Hitesh Apr 10 '18 at 13:43