Duplicate Target: Xcode cannot work with the selected destination

Question

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

Fixed copying .plist in build settings, removed spaces from the new product name. It is impossible to find the difference with the original target settings, it is still a terrible mistake. Any ideas?

Answer 1

With Xcode 4.5.2. (4G2008a) this question seems to have disappeared. Now I can duplicate the original goal, correct the product name and get the application running correctly.

Answer 2

I got this error when I opened an old project under Xcode 4.5. Problem. In the build setup, a standard architecture was installed, which means 64-bit and 32-bit, while the minimum deployment target was set on OS X 10.4.

Setting a minimum deployment target in OS X 10.5 resolves the issue.

Answer 3

When I ran into this problem, on top of the xcode window, I changed my Mac 64-bit to a 32-bit Mac. It worked for me.

Answer 4

For me, this was a mismatch between the name of the executable file, as indicated in the "Product Name" in the settings of the target assembly, and the name of the executable file specified in Info.plist. In fact, when you duplicate the target, you get the “copy” suffix, which you usually change immediately, and this can lead to some errors.

An additional indication of this discrepancy may be visible when you select a product application in Xcode and open it in Finder. If the application icon is superimposed using the stop sign, here it is, your application is not executable.

Answer 5

If everything looks good, the last thing you should check is the contents of your application. Most likely, the file name Info.plist of the application name does not match what you have in the assembly configuration.

Answer 6

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

Answer 7

I got the same error message after accidentally copying the binary to / usr / local / bin. The binary was “manually” generated by the Makefile — the Xcode (5.1) build process was configured to place the binary in / usr / local / bin. Removing the manually created file and starting the build resolved the issue again.