Geek Answers Handbook

Ready Launch <App> on iPhone 6.1 Simulator

I am developing a new application for Iphone using Xcode (version 4.6 (4H127)) and the iPhone 6.1 simulator (Versión 6.0 (369.2)).

In the beginning, everything was wonderful: every time I clicked the “run” button, the application was loaded into the simulator, and I was able to test it. But sometimes it doesn’t work: when I press the start button, I get the message “Finished on iPhone 6.1 Simulator”. The code compiles successfully (only minor warnings).

enter image description here

The main problem is that when I get this message, the only way to use the simulator again (in this project, the other xcode projects work fine) is to start a new project and add each file to it.

I tried to delete the derived data, restart the simulator, restart the computer, etc. Even I took a snapshot when the simulator was working, but when I return to the snapshot state, the simulator still does not work.

What can I do? Any idea?

+6
source share
6 answers

1. Launch iOS Simulator.

2. From the "iOS Simulator" menu, select " Reset Content and Settings ",

3. Close and rebuild your application.

+11
source

This problem may occur if you have problems with targeted membership in the project. . Select the info info file from the folder structure of the project navigator Supported files , go to the toolbar of the interface toolbar (the "Utilities" section in the "View in the upper bar" section), then find the Target membership in the "File inspector" panel, if it is installed, uncheck . Clean and create, hope this helps.

+2
source

Library > Application Support > iPhone Simulator > 6.1 (or whichever you're using) > Applications > Your Application and delete it.

enter image description here Restore your application and restart.

+1
source

I had the same problem, with the same "failed to connect to process id 0" (I actually did not notice this error until I saw that you said you had this error). In one of my projects, Simulator 6.0 did not work, but it works in my other projects. My simulator 5.1 also worked.

What worked for me was based on this other answer to a similar question: fooobar.com/questions/55062 / ...

  • Go to the Product menu and find the Edit Schema menu there.
  • In the "Edit Schema" window, select "Launch" on the left side of the screen, and then on the right side, change the debugger from LLDB to GDB.
  • Run the project, it worked in the simulator.
  • Then go back to Edit Scheme and go back to LLDB.

I noticed that you tried to configure the debugger on GDB, and not on the debugger, but you thought that I would say that it helped me, since you helped me figure out my problem (that is, I couldn’t see process message ID 0 ".

+1
source

This problem may occur due to the presence of more than one info.plist file .

I also ran into a similar problem and eventually found that when adding some resource file from another project, I also added its info.plist file.

After checking Build Phases> Copy Package Resources , whether another info.plist file exists there or not. If it exists, delete it, clean the project and rebuild it. Hope this helps .....

+1
source

I came across the same issue and somehow managed to fix it, and almost immediately he returned to breaking. I can say that broke it, though.

I added a couple of folders (links to folders) with files in them to the package resources section. It broke him. If I remember correctly, I deleted both of them and fiddled with DeploymentTarget. I may have reset the simulator before. Despite this, he began to work. In this way,

  • there is hope for correction
  • This thing is caused by folder resources that need to be copied to the package.

Updated:

I was able to get it working again. Here is what I did. - Resetting the derived data folder - Close the simulator application - The deployment in the simulator folders has also been cleared (Users / XXXXXX / Library / Application Support / iPhone simulator / 6.1 / Applications)

Since the last time adding folders to the package made it lock, I tried this step by step, adding one folder to the kit and trying. It turns out that one of my folders was named "Resources", and it became clear to me that a particular name could potentially run into something else that the application was looking for. So I renamed this folder to Res and tried it. Now it works.

So you have it. Follow the steps above to get rid of the problem. Avoid copying folders called Resources to your package.

+1
source

More articles:


All Articles