Xcode cannot work at selected destination

Question

This morning I started my application, and now all of a sudden I get the following error when I try to start the iPhone 5.1 simulator.

Cannot start the selected destination.

The destination does not support the architecture for which the selected software is built. Navigate to the destination that supports this architecture to run the selected software.

I deleted the circuits, but still haven't decided.

I am using Mountain Lion. I am using xCode 4.4 (recently updated to Mountain Lion and xCode 4.4)

UPDATE 1: Here is a view of my build settings:

UPDATE: Here is the actual error that prevents its execution.

Answer 1

You can follow these steps:

• Quit Xcode and iPhone Simulator
• Disconnect your devices.
• Go to /Users/your_usr_name/Library/Developer/Xcode/DerivedData/
• Delete all data in this folder
• Run Xcode again and run the project

Hope this solves your problem.

Answer 2

I had a problem after upgrading from SDK 3.1 to Facebook SDK 3.1.1. I think it's my fault.

Inside the "resources" folder there is now an absolutely useless but dangerous info.plist, which, if imported, can break your project file. I don’t know why they turned it on, but I believe that some of us have made the same mistake recently.

Answer 3

I found this problem with Xcode version 4.4. And finally, I solved it like this:

Find "Info.plist" in your project, then deselect the target membership plus in the right window window, it works for me.

Answer 4

You can also check if the project uses a supported compiler in the project settings.

Answer 5

Its just a duplicate Info.plist file, just use 1 Info.plist file in the files, then restart xcode it fixed for me

Answer 6

I just encountered this error in Xcode 4.5.1, and the error disappeared after I deduced all non-alpha characters from the Product Name assembly setup.

Answer 7

I believe this may be the current unregistered error with Xcode 4.4+. I / had the same problem with my project. I uninstalled all versions of Xcode and restarted with 4.4, opened my project and got an error again.

Then I started a new project with a template with a different name. There was no problem.

Then I renamed my old project, started a new empty project with the same name and created / started and got an error again. This new project was nothing more than a view controller that did nothing. I should have got a blank screen, but got the same error as you.

Frustrated, I closed it for a day and restarted the old project, and it worked. I have not changed anything. I currently have the error again, and neither rebooting nor restarting Xcode fixes it.

So, in general, a project cannot have absolutely any changes, sometimes it builds and works fine, sometimes you get this error. For the record, I did not get this error when starting Xcode 4.3.

My problem did not appear until I upgraded to Mountain Lion and Xcode 4.4, which ended up on the same day. Now I can not return to a 100 percent workable configuration.

Answer 8

Completing my files in SVN and checking the project in a new directory fixed this for me.

Answer 9

Look at both the project and the build targets on this architecture and see if anything has changed. When you first go from Xcode 3 to 4, it uses hidden chaos, giving the same error, and in the end you need to add i386 to the line "Real architectures". I just looked at my big project running in Xcode 4.1 and it shows nothing about i386 etc. But I have other newer projects where I get this highlighted thing in this line $ (ARCHS_STANDARD_32_BIT).

EDIT: I accepted this offer with a guru friend. None of us can find a connection with i386 in our projects - Xcode uses some magic. However, I got hit on i386 in a binary plist inside the project, which leads me to another suggestion.

In the build settings, make sure ALL "Architectures" are $ (ARCHS_STANDARD_32_BIT).

If this does not work, we suggest you look at the compilation lines and ld of your assembly when you select iPhone 5.1 Simulator in the circuit menu - to see if it is really i386,

Another idea is to transfer all your schemes and user settings to a save folder somewhere (with a closed project), then open and recreate the scheme again. Now try again. There is no link to i386 in any of my project.pbxproj files, so our suspicion is that it has something to do with setting up the circuitry for the target device.

Good luck

Answer 10

I decided to change the key "Build options" from "armv7" to "normal" both in the project and in the settings of the target assembly

Answer 11

in addition to deleting all files in this directory Users / your _usr_name / Library / Developer / Xcode / DerivedData /

I restarted my Mac and it worked fine (rebooting xcode and the simulator didn't cut for me)

Answer 12

I ran into this problem. In my case, it turned out that I changed the name of the Bundle for my project with multiple targets instead of the product name. As soon as I fix this by editing the project name correctly and then returning the Bundle Name to $ {PRODUCT_NAME}, it will run again in the simulator.

This may not be the answer for everyone, but it shows that product misappropriation errors (special characters, spaces, etc.) are the source of many, and this made me reconsider the renaming that I had.

Answer 13

I ran into the same problem with my project. Here is a brief explanation of the situation and my solution. This may or may not work in your case.

I work in a place where there are several iOS projects. I recently upgraded to Mac OSX 10.8 and Xcode 4.4.1. I was working on a project that was originally built on Xcode 4.1 for iOS 4. Since Xcode had iOS 4 simulators up to 4.3, the project was built and worked perfectly on all simulators. However, in Xcode 4.4.1 I did not find iOS 4 simulators, and there is no easy way to install them, so I get the message "Can not run at selected destination". This is how I got my project to run.

• Select the Build Settings > Architectures check box and set the architecture to all Standard (armv7) or ${ARCHS_STANDARD_32_BIT} for all your profiles.

• In my case, install the Base SDK in Latest iOS(<ios version #>) 5.1.

• Set Build Active Architecture Only - NO for all profiles.

• Install Valid Architectures in armv6 armv7 for all profiles. You may need to add either depending on what is already available.

• Install iOS Deployment Target in iOS 5.1 (in my case).

• Make sure you have the same goal under the Deployment Target on the Summary tab of your project.

Clean and run and cross your fingers!

Answer 14

In my case, the problem occurs after deleting the entire Resources folder, copying the Resources folder from another or old project on top of the current one, and then adding this folder.

I solve the problem with the Analyze tool: after analysis, it heats me in Info.plist inside the "Copy Bundle Resources".

Just go to the "Copy Stock" tab (on the "Build Phrase" tab), delete Info.plist, then restart Xcode, clean and create. My project has returned to normal.

Hope help someone :)

Answer 15

I think that many of these decisions make me completely rebuild, which is what solves this for me.

I did Product => Clean and the problem disappeared.

Answer 16

This worked for me: - Check if all product links are consistent in the settings and plists. Also check that the product name does not contain spaces or other “illegal” characters.

Answer 17

try renaming your project. I decided that way.

Answer 18

Judging by the answers, this type of error has many potential sources, so here is my (admittedly careless) version of the error (and a simple solution):

• Xcode project configuration parameters can be set at two levels: project level and target level. For those less known, the target level is where you have the executable application, and often other elements, such as building a dynamic library.
• In the "Linking" section of the assembly settings, there is an option for the Mach-O type, where you can install an executable, dynamic library, static library, etc.
• I had problems preparing a dynamic library, checking build parameters for a project, and saw that Mach-O was empty. So I installed a dynamic library. Then I continued to review other things and forgot that I made this change. But I did not understand that I was at the general level of the project, and not at the target level for a real dynamic library. This changed all the Mach-O target settings to a dynamic library.
• And, of course, the executable did not like it when it was considered as a dynamic library, and I received an OP error message.
• Installing the executable back to the Mach-O executable in the build settings at the target level eliminates everything. Annoyingly, at the project level level, we were still talking about a dynamic library, but with the correct settings for the target level, everything worked fine.

Stupid I know, but since a couple of the more radical solutions listed above would have been indirectly resolved for this error, I thought I would share that someone else made the same mistake!

Answer 19

The way I solved this error was to add a dummy function to my project. My problem was My application did not have its own code, only related code .

I have an unusual situation with two projects: one parent of the "Application" and one "Engine". All the compiled code is in the child, and the parent simply binds to the child, copying a ton of resources related to the App to the project.

Apparently, this is sad Xcode, resulting in the above error.

My solution adds this C function / file to the application project:

int workaround_for_xcode_reporting_cannot_run_on_selected_destination(){return 0;}

Answer 20

I am recovering data from a time machine. Please note that this is the same data that was saved just 1 hour ago. The problem started yesterday. Thus, it must be EXACT same data. \

But it works.

Answer 21

I tried everything that was said here. Nothing succeeded. It seems like I somehow imported Info.plist twice. To fix this, I selected the project and clicked on the "Check Settings" button. Subsequently, he works for me.

Answer 22

In the afternoon of the experiment, I think this means that the debugger cannot find your executable file to run. I think this is an important difference from the previous answers, because this is the main reason that can have many symptoms. In my case, he was unable to reconcile Info.plist applications for custom assembly, where we copied plist for assembly. I changed the build setting to Alt-Info.plist for AltDebug and fixed it. Also meant no more copying.

Your main reason may be different, so the key conclusion is to think about why Xcode might not find your built application.

Answer 23

You will be glad to know that this problem has a very simple solution. Select Info.plist in the project navigator tree and make sure that it is not assigned to the target. I have confirmed that this is the right decision. If you are building iOS 6 or earlier, you may also need to add armv6 to supported architectures.

Answer 24

I had this problem after upgrading to Mountain Lion and Xcode 4.4.1 for an OSX project. To solve this problem, I had to upgrade the deployment target to 10.5 or higher; It was set to 10.4 and higher.

Answer 25

You have to find the Xcode process in the "Activity Monitor" and kill it! I just did it to solve a similar problem!

Answer 26

I had this problem after accidentally deleting the Resources folder when I added it again to the project, Bam!

I also use Mountain Lion and Xcode 4.4!

trying to figure out what causes this, but it seems to play when it is deleted, and then adds the info.plist file! can anyone confirm this?

Answer 27

I had the same problem after two events:

• I updated to version 3.0 SDK for Facebook.
• I updated my OSX (with a minor version upgrade).

The only fix worked out by me was to add armv7s (of course, “s” at the end !!!) As suggested here: https://stackoverflow.com/a/312618/

Answer 28

Another solution: after trying everything in the list above, I fixed it by referring to the warning that the TestFlightSDK1 path was not found. To do this, I deleted the corresponding path from the header search paths (assembly settings> search paths) and deleted TestFlightSDK, and now everything will work fine.

Answer 29

I had this from the beginning, and it looks like the problem is that the emulator cannot process virtual smart cards. Unfortunately, I just used my Android phone connected via USB.

Answer 30

Extract Info.plist from the build phase of the Copy Bundle resource. It worked for me!