7

In xcode, I tried to add a tap gesture to my app and when I built it, it started a problem with Xcode. It goes from building, 'running on iPhone 6.1 simulator' to 'finished running on iPhone 6.1 simulator'.

If the simulator is closed, it starts up with a black screen and you cannot click the home button etc. If open, nothing happens, the app doesn't install but the simulator doesn't crash.

I have tried the armv6 architecture 'fix' but that didn't work. I have also cleaned the project and project data. I have reset the simulator multiple times as well.

If I add the old files to my new project, it works up to a point (I copy and paste old files into new) but then the same happens.

Thanks for your help in advance!

NOTE: New blank projects build and run fine.

EDIT: It still didn't work after undoing my previous actions, and the simulator is responding according to Finder, although the screen stays black

–––––––––––––––––––––––––––––––––––––––––

UPDATE

I had a folder named 'resources' in my application, imported as a reference which, following links from the thread @arthan.v supplied me with fixed the problem. What I did was rename the folder to files and reimport it.

Thank you so much, I spent 2 days trying to fix it before now!

ABC
  • 718
  • 8
  • 23

4 Answers4

6

Click the Center Button in View on your right hand side of Xcode.
enter image description here

In your Bottom bar, you'll see error: failed to attach to process ID 0.

Check these error: failed to attach to process ID 0 and Xcode compiles my App, but can't run it in the simulator

Community
  • 1
  • 1
arthankamal
  • 6,341
  • 4
  • 36
  • 51
2

This sometimes gets fixed by these steps:

  • iOS Simulator > Reset Content and Settings ... > Reset
  • Xcode > Build and Run
maz
  • 8,056
  • 4
  • 26
  • 25
1

I experienced the same issue after I had re-organized some code and renamed the workspace and project. Eventually realized there was an old version of my test app on the simulator's homescreen. I delete that and then everything was building fine again.

jfroom
  • 660
  • 7
  • 17
1

You might need to add the device to the provisioning profile. I experienced this on Xcode 6 and a real device.

jomafer
  • 2,655
  • 1
  • 32
  • 47