4

(OS X, not iOS): "Choose a destination with a supported architecture in order to run on this system"

Fixed the copied .plist in the Build settings, removed spaces from the new product name. Can't find any difference with the original target's settings, still this dreaded error. Any ideas?

RickJansen
  • 1,615
  • 18
  • 24

7 Answers7

3

I got this error when I opened an old project under Xcode 4.5. The problem: The build setting were set to Standard Architecture, which means 64bit and 32 bit, while the minimum deployment target was set to OS X 10.4.

Setting the minimum deployment target to OS X 10.5 fixes the problem.

DavidPhillipOster
  • 4,195
  • 1
  • 19
  • 17
1

When i faced this issue, on top of the xcode window i changed My Mac 64-bit to My Mac 32-bit. It worked for me.

AMIC MING
  • 6,306
  • 6
  • 46
  • 62
1

For me it was a mismatch between the filename of the executable, as specified by "Product Name" in the target build settings, and the executable filename indicated in the Info.plist. In fact, when you duplicate a target, you get a "copy" suffix that you usually change right away, and this may lead to some mistakes.

An additional indication of this mismatch can be seen when selecting the product app in Xcode, and opening it in the Finder. If the app icon is overlayed with a kind of "stop" sign, here it is, your app isn't executable.

onekiloparsec
  • 2,013
  • 21
  • 32
1

If everything looks alright, one last thing that you should check contents of your app. Most probably application name Info.plist file does not match what you have in your build configuration.

Nitin Bhatt
  • 428
  • 5
  • 13
0

With Xcode 4.5.2. (4G2008a) this issue has gone away, apparently. I can now make a duplicate of the original target, fix the product name, and get a properly running application.

RickJansen
  • 1,615
  • 18
  • 24
0

I started getting the same thing. I did a Clean and it seems to have fixed it. Lion/Xcode 4.6.2

Dave Higgins
  • 141
  • 2
  • 3
0

I got the same error message after accidentally copying a binary to /usr/local/bin. The binary was "manually" generated by Makefile - the building process of Xcode (5.1) was configured to place the binary in /usr/local/bin too. Removing the manually generated file and starting the build again fixed the problem.

EddyBrown
  • 1
  • 1