Choose a destination with a supported architecture in order to run on this device

Question

enter image description here

my Xcode is Version 4.4.1

The project worked perfect before updating to this newer version, but now it stopped working

Ok, not sure if this is the Problem in Your Project. But what fixed it for me, was to change the Name of the Info.plist File. 1. I changed the name from Info.plist to my-project-info.plist 2. also change it under target-build-settings/Packaging/Info.plist 3. Than delete the App from Devices/Simulators and re-run the App through Xcode In my Case, everything worked fine since than. In my Case **there was nothing wrong with the specifications made in the plist file or with the valid architectures**. — Oleg Hein, Sep 05 '13 at 15:58
My Solution Find Here: http://stackoverflow.com/a/20798054/1092219 — Himanshu Agnihotri, Dec 27 '13 at 09:26
It's a compiler issue, you can set the 'Compiler for C/C++/Objective-C' flag under build options to default or Apple LLVM 5.0. — Say2Manuj, Feb 27 '14 at 06:59
Target -> Build Settings -> Build Options set the "Compiler for C/C++/Objective-C" - "Default compiler (Apple LLVM 5.0)" and the issue will be solved — Jayaprada, Mar 13 '14 at 08:39

score 39 · Accepted Answer · answered Jun 18 '13 at 05:44

39

I have had the same issue when making multiple targets. My issue was that I had to change my Product Name under Packaging.

In each target project > Build Settings > Packaging -> Product Name

answered Jun 18 '13 at 05:44

M Jesse

2,213
6
31
37

1

this fixed it for me, opening an old project on my Mac – Tiago Aug 23 '13 at 19:43
131

Had same problem on my project. Build settings-> Complier for C/C++/Objective c was set wrong. I changed it to default compiler available, it worked!! – Kiran S Nov 13 '13 at 06:22
1

Thanks M Jesse - Did it for me. – Ralpharoo Jan 03 '14 at 18:55
Just rename Product Name with the same name,and it worked~ – HamasN Jan 08 '14 at 09:14
3

@iphonegeek thanks. Build settings-> Complier for C/C++/Objective c when changed to default compiler available, solved my problem. – girish_vr Feb 15 '14 at 07:45
@KiranS you should make an answer with this comment. – Khaled Annajar Sep 07 '14 at 22:50
@khaledannajar: not sure how ? seems the question is closed – Kiran S Sep 10 '14 at 16:02
@KiranS You are right I did not notice that. :) – Khaled Annajar Sep 12 '14 at 20:08

score 27 · Answer 2 · answered Sep 27 '12 at 12:22

27

I wanted to install my old application on iPad. I updated the my XCode from 4.3.2 to XCode 4.5 and having this problem.I tried searched alot finally got this solution.

In your target settings (not project settings), please check the following settings there

Valid Architectures : armv7

In my case, there was arm6 which i removed from it and it works. Hope this helps :)

answered Sep 27 '12 at 12:22

iNeal

1,729
15
23

1

What do you lose by removing the arm6? Surely you are sacrificing compatibility or something? – bkbeachlabs Jan 21 '14 at 16:04

score 8 · Answer 3 · answered Mar 27 '13 at 13:34

8

Had the same issue today. If you have added any file check if you didn't also add info.plist with the files. Remove that and it will work.

answered Mar 27 '13 at 13:34

LetynSOFT

134
1
8

Please note that Info files may exist under one of your "Library Search Paths" directories. and not necessarily added to your project files! (took me hours to notice) – AmitP Mar 17 '14 at 16:53

score 3 · Answer 4 · answered Apr 05 '13 at 03:07

3

In your Info.plist remove a string "Required device capabilities armv7"

answered Apr 05 '13 at 03:07

OrdoDei

1,379
2
16
9

score 2 · Answer 5 · answered Sep 28 '12 at 20:51

I had this same error message thrown at me today.

I was working in a workspace with a few iOS App projects and a Framework project (using https://github.com/kstenerud/iOS-Universal-Framework). I had just added that Framework project and tested things out in the iPhone emulator, but when I went to just fire up any of the apps on my iPhone, they all threw this error (mentionned above).

Turns out I fixed the problem by just removing the Framework project from the workspace. I could use the framework from within an iOS app without trouble, but the framework project could live in the same workspace for some reason.

Hope this helps anyone in my situation!

score 2 · Answer 6 · answered Apr 22 '13 at 19:31

2

I just ran into this issue I had added the Info.plist from the Facebook SDK 3.5 to my Xcode project. As soon as I removed the facebook Into.plist file everything worked.

answered Apr 22 '13 at 19:31

ribeto

2,038
1
16
17

score 2 · Answer 7 · answered May 30 '13 at 04:52

2

In your Info.plist remove a string "Required device capabilities opengles-1"

answered May 30 '13 at 04:52

Jarson

123
4

Choose a destination with a supported architecture in order to run on this device

7 Answers7