Xcode 4 hangs at "Attaching to (app name)"

Question

I just upgraded to Xcode 4 and for some reason my app won't run in the simulator or iOS device. It was working perfectly in Xcode 3, but all of a sudden now when I press run the program stops at "Attaching to...". There doesn't seem to be any other info to help with this problem either.

For summary you can try following things to tackle the issue:

Restart the simulator.
Make sure that you haven't included the Info.plist file in your Building Phases -> Copy Bundle Resources.
Resources folder added to the project as a folder reference (the blue folder icon). That caused the trouble, after adding the folder as a group the problem went away.

I also have this problem, a restart of xcode often fixes it temporarily, but it always comes back. — NWCoder, Mar 21 '11 at 20:14
Yea I had it with my other app too and was able to solve it by restarting, but this one won't run no matter what. Tried restart, iphone sim, ipad sim, ios device... nothing works — Rob, Mar 21 '11 at 20:58
I have been getting this when i added a directory to the project that is not a group but a regular folder. Specifically, when there is an added folder that has a name conflict with a group or file in the main project. — yeahdixon, Sep 26 '11 at 16:09
I got this issue when I draged a `resources` folder into the project. Deleting it doesn't fix it. — Kit Sunde, Nov 03 '11 at 18:52
@KitSunde I dragged a `resources` folder into my project as well. Maybe that's the problem? How did you resolve it? — joshim5, Nov 10 '11 at 20:47
@joshim5 I just deleted the project and created a new one since I was only doing a simple UIWebView app that took 5 minutes to setup. — Kit Sunde, Nov 11 '11 at 02:43
Just change the debug option from LLDB to GDB by editing the scheme. (Worked For Me) http://stackoverflow.com/questions/10147356/xcode-4-3-2-wont-attach-to-debugger — Ansari, Jun 25 '12 at 13:35
It solved the problem: Make sure that you haven't included the Info.plst file in your Building Phases -> Copy Bundle Resources.By @RonnyD1978 — user739711, Aug 12 '12 at 12:50

score 104 · Accepted Answer · edited Dec 24 '22 at 03:57

104

Fixed it!! Hopefully this helps some people avoid a very frustrating couple hours. I solved this by:

Clicking on the project name in the left pane (at the very top). This will bring up a new menu to the right, something like the project/ target editors in XCode 3.
Click on Build Settings up at the top.
Under Packaging make sure your product name is the same for every build, and equal to whatever it says it's attaching to. Eg if XCode is Hanging at "Attaching to myLCBO" but your product name is "LCBO Finder" then it won't build. That was exactly my problem because I renamed my app half way through development.

edited Dec 24 '22 at 03:57

starball

20,030
7
43
238

answered Mar 21 '11 at 21:16

Rob

7,028
15
63
95

Yea I don't think it always works, but it's definitely one of the issues you might encounter – Rob Apr 01 '11 at 05:41
This doesn't fix the error for me. Using XCode 4.0.1, I start a new project, build and run it without modifying the default template - works. Without quitting the simulator, I make some changes, run again, still works. Then I quit XCode and the simulator, next time I run - hangs at "attaching to ". – Tomas Andrle Apr 04 '11 at 23:16
And clean all targets (Xcode 3.x) or Clean product (Xcode 4.x). This helped me when I thought this solution does not work. – Lukasz Apr 18 '11 at 09:37
Thanks, this resolved the problem for me too. For some reason the debug product name was incorrect whereas the release one was correct. – Andy Bowskill Apr 25 '11 at 22:09
I had the same behaviour, but I had to change the iOS target property "Application requires iPhone environment" from "YES" to "NO" to get it to work. – nikkumang May 07 '11 at 06:43
17

Try this: Reset Simulator, Clean Build, Quit Simulator, Run Project. Should work. – Jordan Jun 16 '11 at 11:38
I don't know how ya's done it, but I know YA'S DONE IT!! Dude, saved me tons of time. Thanks! – gonzobrains Jul 08 '11 at 06:39
4

@Jordan: didn't help, but rebooting did. Lion bugs bigtime for me and my Mac mini. – Jonas Byström Nov 02 '11 at 10:20
One additional note; if you've tried **everything** discussed here and you still get this problem, check to see if your app is deadlocking on the main thread. I was having a lot of frustration with this issue, and finally found that a coding bug was causing the main thread to get stuck. – aroth Jul 22 '12 at 13:48
This fixed my problem, however it does not fix the problem that I need to rename my product for this specific target. How can I get around this problem by changing XCode's expectations rather than having to change my product name to fit XCode's expectations? – Ahab Aug 16 '12 at 19:20

score 72 · Answer 2 · edited Nov 06 '12 at 06:50

72

Here was our fix:

In Project > Edit Schemes > Run.

Change the Debugger from GDB to None (directly above the green circle in the image above).

edited Nov 06 '12 at 06:50

Himanshu

31,810
31
111
133

answered Jun 04 '11 at 20:45

InterThread

61
3
2

This helps for me too, but obviously, there is no bug reporting on errors, just NSLog support – oberbaum Jan 09 '12 at 18:23
13

This fixes it for me, but I really wish I knew why/how to actually fix it. It was actually LLDB that was causing it. Switching to GDB works fine. – justinxreese Apr 30 '12 at 00:30
4

Thanks, fixed the issue but not the problem. Apple needs to try using their crap before releasing it. – Stephen Punwasi Mar 31 '13 at 22:25
I tried all the other tips on this page. Then, switching debugger from LLDB to none did the trick. Thanks! – thomax Oct 17 '13 at 18:27
Works, and working with NO debugger it enables you to work faster.. Of course, if you need to debug, switch it back on. – Matej Dec 20 '13 at 23:47
It's worth noting that this solution mentions 'Project > [...]' this might be available in other (older) versions of Xcode but in mine it's named 'Product > [...]' (as in the answer of @macnico ;) – Tommy Bravo Jan 11 '14 at 22:51

score 40 · Answer 3 · answered May 03 '11 at 08:34

40

A tip I found at the Apple Developer Forums:

Go into your ProjectName.xcodeproj/ directory and delete anything named with your userid. Re-open the project in xcode and all that will get recreated and it should work. At least it did for me.

Another tip is to manually delete the build directory.

Yet another tip is to navigate to the Organizer (Shift ⇧ Command ⌘ 2 in xcode 4), select Projects, select you application in the left hand side and then the Delete...-button to the right of Derived Data.

And never forget the universally useful tip: restart your computer and try again.

Good luck!

answered May 03 '11 at 08:34

Pål Brattberg

4,568
29
40

7

believe it or not, I tried everything on this page and restarting xcode multiple times without success. I finally just rebooted my machine, and then it worked. Crazy. I thought that was only a Windows solution :) – dreyln May 11 '11 at 19:40
1

I had exactly the same problem and deleting everything with my userid and restarting Xcode resolved it. – Nikita Zhuk May 17 '11 at 07:28
Deleting the derived data worked for me (3rd tip). This problem happened when I added files to an XCode project and this solved it. – Jonathon Horsman Jun 30 '11 at 07:44

score 28 · Answer 4 · edited Apr 12 '11 at 20:16

28

Solution provided didn't fix the problem in my case.

In order to solve it (XCode 4 only), I had to go to Product -> Edit Scheme. Then select the "Run " scheme, and marked "Automatically" which wasn't enabled.

Hope it helps someone.

edited Apr 12 '11 at 20:16

sudo rm -rf

29,408
19
102
161

answered Apr 12 '11 at 20:11

macnico

206
2
3

Win! Saved me a bunch of headaches. Thanks! – Jon Jul 18 '11 at 19:51

score 21 · Answer 5 · edited Nov 04 '21 at 21:51

21

For everyone still trying to resolve this after everything you tried from above, try reseting the iPhone Simulator.

Simulator > Device > Erase All Content and Settings...

This will erase all apps from simulator, but now you can finally use simulator!

edited Nov 04 '21 at 21:51

pkamb

33,281
23
160
191

answered Apr 16 '11 at 15:36

Dunja Lalic

752
13
26

1

tried this - didn't do anything. macnico's solution above worked for me. – Kwexi Jun 28 '11 at 01:13

score 11 · Answer 6 · answered Jan 18 '12 at 16:50

11

Also: make sure that you haven't included the Info.plst file in your Building Phases -> Copy Bundle Resources. If so, remove it from that list! I small mistake which could happen, but something that messes things up quite nasty :S

answered Jan 18 '12 at 16:50

RonnyD1978

1
1
2

Thanks!! that was my problem, none of the other answers worked for me. – Damian Mar 19 '12 at 17:48
After trying everything, your solution was the one which worked. THANKS! – jcdmb May 17 '12 at 07:37

score 10 · Answer 7 · answered Aug 04 '11 at 16:16

10

Restarting simulator works for me :)

answered Aug 04 '11 at 16:16

Prabh

2,466
2
24
27

score 8 · Answer 8 · answered Sep 14 '11 at 17:58

8

One more possible solution: I had my Resources folder added to the project as a folder reference (the blue folder icon). That caused the trouble, after adding the folder as a group the problem went away.

answered Sep 14 '11 at 17:58

zoul

102,279
44
260
354

Weird but true, Xcode4 does not seem to like folder references. Solved it for me. – Till May 08 '12 at 17:45
Same here, Apple, really? – Ege Akpinar Aug 03 '13 at 01:34

score 5 · Answer 9 · answered Dec 28 '11 at 05:58

5

I really find the answer for me :)

for me,

project setting -> your target -> build phases -> validate setting -> perform

and now the problem is gone.

:)

I hope someone it help

answered Dec 28 '11 at 05:58

sapsaldog

41
1
3

Thanks! That fixed it for me. I had never seen the 'validate settings' button. – Sunil Gowda Apr 03 '12 at 05:24

score 4 · Answer 10 · answered Aug 18 '11 at 03:00

I solved this problem how:

1) iOS Simulator->Reset Contents and Settings...

2) Sure project name, scheme name and target name is identical. "AppName" and "Appname" is not true. Must be "AppName" and "AppName", or "Appname" and "Appname".

3) Restart XCode and Quit Simulator.

Project name at Build Settings->Product Name.

Scheme name at Product->Manage Schemes. Click on current scheme once for rename.

Target name at Column of Project with Targets. Click once on current target for rename.

Good luck =)

score 3 · Answer 11 · edited May 14 '12 at 09:05

3

I tried everything in this page, and the "new" solution that worked for me was to go into the simulator, and "Reset Content and Settings" in the iOS simulator main menu.

edited May 14 '12 at 09:05

Nate

31,017
13
83
207

answered May 13 '12 at 23:31

philippe

1,877
2
20
25

score 3 · Answer 12 · answered Dec 05 '12 at 07:30

3

This solution is not technical but it worked for me.

When Attaching to Process shows up in xcode and it hangs for a while, just quite the iOS simulator and re-launch the app by pressing Command + R.

It will launch the app without any issues :)

answered Dec 05 '12 at 07:30

Basheer

1,207
9
10

score 3 · Answer 13 · answered Apr 01 '11 at 13:35

3

Like Rob said, but also check the "identifier" should read by default "com.yourcompany.YourAppName" I had changed the "yourcompany" by mistake and this caused the same issue noted above.

answered Apr 01 '11 at 13:35

Jason

650
2
10
33

You solved it for me! Curious to know the correct way to change "yourcompany". – Andrew May 05 '11 at 23:31
check out this link to change it the correct way. (http://stackoverflow.com/questions/2956464/where-do-i-set-my-company-name/5264348#5264348) – Jason May 06 '11 at 02:22
Thanks a ton.. I tried all of the above but nothing worked!! wish I could give you 100 votes up :P – Ahmed Dec 14 '11 at 15:39

score 3 · Answer 14 · answered Nov 11 '11 at 19:48

3

This also seemed to happen to me when the info.plist file was in the copy build phase. It appears that sometimes Xcode will warn you about this, and other times it won't. Very strange. But if you are experiencing this issue, make sure that info.plist is NOT in your copy build phase.

answered Nov 11 '11 at 19:48

Morgan

1,765
2
19
26

I had setup a folder structure by drag & drop and Xcode added them to the "Copy Bundle Resources" build phase. Removing the folders from that phase fixed it for me. – fphilipe Mar 05 '12 at 14:29

score 3 · Answer 15 · answered Jan 01 '12 at 19:55

3

My problem was also a folder named "resources" on the root source folder. Looks like it conflicts with some internal build naming.

Renaming the folder to "res" solved the problem for me.

answered Jan 01 '12 at 19:55

Rangel Reale

698
6
7

score 2 · Answer 16 · answered Sep 23 '12 at 23:36

2

Under Product > Edit Scheme > Run > Info, changed the Debugger from LLDB to GDB worked perfect for me!

answered Sep 23 '12 at 23:36

Leo Correa

19,131
2
53
71

score 2 · Answer 17 · edited Oct 17 '11 at 05:35

2

For me, none of these has worked. I realized that my project had 2 info.plist files (with two different names, like info.plist and Project-info.plist), so XCode got confused. I just removed the incorrect plist file, and it worked!

edited Oct 17 '11 at 05:35

PengOne

48,188
17
130
149

answered Jun 03 '11 at 16:34

jpmtrabbold

29
2

This was it for me, I tried many other things suggested by others. If you created a new Xcode4 project and tried to add in your old files, this might be your culprit. – zekel Jan 10 '12 at 19:56

score 2 · Answer 18 · answered Jun 15 '11 at 00:09

2

I tried everything and nothing worked. I have an old project from XCode 3. I simply renamed info.plist in the project to another name, restarted the simulator and everything is working fine since.

answered Jun 15 '11 at 00:09

Eric Reiher

1
1

+1 Renaming MyApp-Info.plist to something else broke my build, but renaming it back again magically fixed the hang at "Attaching..." for me. – Ergwun May 01 '12 at 05:23

score 2 · Answer 19 · answered Oct 17 '11 at 05:34

I frequently encountered this problem after renaming a project in Xcode 4.

I was able to fix it by editing the Bundle Identifier in the .plist file.

After I renamed the project, the Bundle Identifier would change to something like this:

com.yourcompany.${PRODUCT_NAME:rfc1034identifier}

changing it back to this:

com.yourcompany.${PRODUCT_NAME}

will stop Xcode from hanging and allow the App to run.

score 1 · Answer 20 · answered Jun 07 '12 at 16:03

1

I encountered this error after incorporating another project inside my new one. Make sure you delete the project that you have added's info.plist and .app

answered Jun 07 '12 at 16:03

James Morris

163
1
10

score 1 · Answer 21 · answered Feb 07 '13 at 09:01

1

Just came across the same problem: restarting the simulator and Xcode didn't work for me, while restarting my mac worked out pretty well!

answered Feb 07 '13 at 09:01

Chris

4,403
4
42
54

Same here, restarts to the apps didn't work, and restarting the mac did. Also, this problem, for me, cropped up suddenly and mysteriously in the middle of the workday, not as a result of upgrading xcode or any other bigger task. – Joey Mar 19 '13 at 21:09

score 1 · Answer 22 · answered Apr 28 '11 at 12:08

I had the same problem. The issue was there was one more user who was logged in and had the simulator running. Think there can be only one instance of iphone simulator running on a machine even for different users. Hope this info would be useful for somebody :)

score 1 · Answer 23 · answered May 17 '11 at 23:13

What worked for me is the following:

In XCode:

Click on project name
Click on target name
Click on "Build Settings"
Reveal "Product Name" contents (click on triangle)
Make sure the name of all items matches that of project name
- Example
  - Product Name myapp
    - Debug myapp
    - Release myapp
Reveal "Deployment" contents (click on triangle)
Make sure there is a "IOS Deployment Target" item
- Example
  - IOS Deployment Target IOS 3.0
    - Debug IOS 3.0
    - Release IOS 3.0

Then clean and run.

score 1 · Answer 24 · answered May 31 '11 at 14:36

This is what worked for me:

In Xcode navigate to the Product menu and choose EDIT SCHEMES.

In the list on the left choose Run YourAppName.app. From the Executable menu choose OTHER.

Navigate and choose your .app file in your project directory.

Now run and it works :)

score 1 · Answer 25 · answered Jun 09 '11 at 12:49

1

I noticed it happened to me when I edited the scheme from Build Release to Build Debug. I changed back, and it worked :)

answered Jun 09 '11 at 12:49

Lior Frenkel

806
11
25

1

+1 This didn't work for me, but at least I could verify that a release build still worked even if debug didn't. – Ergwun May 01 '12 at 05:24

score 1 · Answer 26 · answered Sep 27 '11 at 08:53

1

What worked for me:

Launch "Monitor" and kill gdb-i386-apple-darwin which was supposedly hung
Restart iOS simulator

enter image description here

answered Sep 27 '11 at 08:53

HyLian

4,999
5
33
40

score 1 · Answer 27 · answered Dec 02 '11 at 07:53

1

My solution is correcting the nib name. (I changed my nib name before for an iPad version but then I deleted the iPad nib file). Then it works well again.

answered Dec 02 '11 at 07:53

Le Tuan Hiep

91
1
3

Kevin Nguyen · Answer 28 · 2012-02-25T00:57:31.697

All of the above suggestion didn't resolve my problem. After I added the Resources folder and and compile, it hangs on attaching to app-name. I removed Resources folder, still hang. I removed the project and recreate a new one ( with the same name ) but still having problem. If it was different name then it's ok. I restarted the OS but still doesn't help.

To solve the issue, I did the following: 1. ps -ef | grep Xcode, and kill all the "Xcode" processes. 2. Reset the content of Simulator, and quit the Simulator. 3. Product > Clean to clean up the build. 4. Compile and run the product. It should work at this point.

Hope it helps some else having this similar issue.

score 0 · Answer 29 · edited Oct 26 '12 at 13:04

0

I think it can be a simulator problem. If your application was built on an old simulator and you are trying to run on the old simulator but your xcode version is new, try to switch your simulator to new version

edited Oct 26 '12 at 13:04

BBog

3,630
5
33
64

answered Apr 11 '12 at 08:28

Rohit Pathak

359
4
16

score 0 · Answer 30 · answered Apr 28 '12 at 14:02

target -> Build Settings -> Packaging -> Wrapper Extension

the value should be app.

for some reason xcode modified the value above to the value of:

Project -> Build Settings -> Packaging -> Product Name

so in my schema i had a funky executable name, like projectName.productName instead of ProductName.app

so double check your schema before you hit command + R.

score 0 · Answer 31 · answered May 24 '12 at 16:53

Unbelievable... I had the same problem, would you like to know which was the exact cause? I added to my project a "blue folder" named "contents". Yes, just renaming the blue folder in anything else resolved the issue. And obviosusly renaming it again to "contents" reproduced the problem.

Hope this may help.

score 0 · Answer 32 · answered Jun 21 '12 at 13:20

I tried all the main tips on this question but it still wouldn't work. Then I went into target Info (in the project settings section). In 'Custom iOS Target Properties' the old product name was appearing in:

Executable file
Bundle display name
Bundle name

I had to change these to match my product name. I then reset the simulator and it worked.

score 0 · Answer 33 · answered Jul 10 '12 at 01:45

Here's what worked for me on 4.3.3 (ultimately):

Erase the Derived Data Folder in XCode. Has no apparent untoward effects.

Go to Finder and Go to folder -> ~/Library/Developer/Xcode/DerivedData/ (Shift-Command-G).

Hope this helps someone who has tried everything else...

score 0 · Answer 34 · answered Jul 17 '12 at 15:19

0

Solved here using Xcode 4.3.3 repairing disk permissions.

answered Jul 17 '12 at 15:19

alexandresoli

918
1
9
18

score 0 · Answer 35 · answered Jul 31 '12 at 15:56

For me the solution was (as many of other people solutions) completely bizarre and rare.

What I did was something silly:

1.- Product -> Edit Scheme -> Run
2.- Click on the "Executable name" (Whatever.app), unfold the optons, and click "other"
3.- Navigate to the "Debug-iphonesimulator" directory and "re-choose" your original non-working Whatever.app filename
4.- Try to run/Clean your project.
5.- Build and Run again against the emulator.

Once I did this, my Whatever.app finally worked :)

(But after many minutes trying ALL things here and some other places, gosh! So frustrating!!)

Big Papoo · Answer 36 · 2012-08-03T13:58:51.730

I was having this very annoying issue since a long time too. I've 3 different XCode versions installed and I'm not sure whether it's the reason or not that none of the above solutions worked for me. But here is the solution I finally found: I don't kill the running Simulator, I just try to launch it again using a Spotlight search, enter "Simu" and you should find it in Applications, then hit Enter. As it's yet running it will magically start my app that was frozen/locked/waiting for attachment. It works perfectly for me now and I hope it will also work for some (all?) of you.

BTW, I call Spotlight with a Cmd+Space, that way it's very quick to unfreeze the simulator without using the mouse.

score 0 · Answer 37 · answered Aug 19 '12 at 03:00

0

This is a bug of XCode 4.4.0 After I updated XCode to 4.4.1, this problem went away.

answered Aug 19 '12 at 03:00

Leo Zhang

3,040
3
24
38

I am on XCode 4.5.1 and I am experiencing this issue. – Krejko Oct 30 '12 at 22:07

score 0 · Answer 38 · answered Aug 20 '12 at 00:28

None of the answers presented here helped me.

I've set up "Launch" radio button in the "Edit Scheme / Info" section to "Wait for MyApp.app to launch" instead of default "Automatically".

It stopped to hang, now it does not start simulator and traces the following in the logs behind the curtains:

error: attach by name 'MyApp' failed
unable to create lldb_private::Process

After trying to google it, this error seems to be a rather rare one.

I do not expect that this error is generic for all cases here, but anyway hope that my post will add some extra details to the discussed issue.

Xcode: Version 4.4.1 (4F1003)

score 0 · Answer 39 · answered Nov 26 '12 at 10:30

0

Xcode failed to attach while the Network Link Conditioner was active. Try to activate it after the attaching has been done.

answered Nov 26 '12 at 10:30

ff10

3,046
1
32
55

score 0 · Answer 40 · answered Mar 21 '13 at 08:35

0

If you are using any kind of FIREWALL software (little snitch, TCP Block etc)

MAKE SURE YOU MONITOR IF XCODE / RELATED PROCESSES ARE BEING BLOCKED.

Once i whitelisted all relevant proceses, the "attaching" issues were solved.

answered Mar 21 '13 at 08:35

sprockett

35
5

score 0 · Answer 41 · answered Apr 21 '13 at 17:56

0

In Xcode 4.6. Just Change Debugger from LLDB to GDB in Edit Scheme.

Product > Edit Schemes > Run

Change Debugger to GDB

answered Apr 21 '13 at 17:56

Darshan

750
7
19

score 0 · Answer 42 · answered Jun 25 '13 at 03:12

I had the problem that in Xcode 4.2 on Snow Leopard 10.6.8 when trying to use GDB as Debugger, it would just show "Running..." but non of the breakpoints would actually work. In fact debugging of the app wouldn't even start.

A quick glimpse at Activity Monitor revealed gdb-i386-apple-darwin would hang at 100% CPU activity.

For me the solution was to reset my heavily customized ~/.gdbinit file (several thousand lines long) which would otherwise work fine when gdb is launched from the command line. As soon as I renamed that file so GDB wouldn't load it everything worked fine.

For the record I had that gdbinit file mess up GDB in Xcode 3.2.6 and Xcode 4.2 on the same machine.

score 0 · Answer 43 · answered Jul 19 '13 at 14:37

Xcode 4.6.3 update (June 13, 2013) resolves the following issue:

Hang when debugging in iOS Simulator on OS X 10.8.4. 13722320

https://developer.apple.com/library/mac/#releasenotes/DeveloperTools/RN-Xcode/

You can try to update your Xcode to see if that works for you.. After installing new XCode version and restarting the Xcode, the problem is solved.

score 0 · Answer 44 · answered May 15 '11 at 18:51

0

After all said and done. I had to stop the simulator. Then the message change to downloading Mac OS X 10.6 core library.

answered May 15 '11 at 18:51

Joseph Bolade Caxton-Idowu

218
3
10

score 0 · Answer 45 · answered May 27 '11 at 14:51

0

Create a new user account, switch to account, open XCode and try running the project. After trying all of the other suggestions with no success, not only was I again able to run on sim, but the original account now works.

answered May 27 '11 at 14:51

gnasher

1,513
12
17

score 0 · Answer 46 · answered Jun 05 '11 at 07:47

I had this problem but the problem was different.

Another application was trying to add a certificate to the keychain and was hanging for some reason (network?). Reproduced this several time, and only when the keychain was free did was xcode able to run the app.

score 0 · Answer 47 · edited Nov 18 '12 at 00:16

I had the same issue.
The app suddenly hangs. After restart the simulator was black and the simulator hanged on "Attaching to ..."

My mistake was the following line in my code:

localnotification.repeatInterval = NSCalendarCalendarUnit; // Buggy, don't copy :)

Probably, the wrong assignment in the localnotification caused the wierd behaviour.

So, it also depends on your code!

So when you haven't changed the project setup and this issue appears, check your code before resetting the project setup.

Alex

score 0 · Answer 48 · answered Jun 08 '21 at 17:51

0

Xcode 12.5 broke iMessage app debugging for me. I can still debug the main app, but when I activate the scheme for the iMessage app Xcode hangs attaching to the app. Downgrading to Xcode 12.4 restored my ability to debug the iMessage app.

answered Jun 08 '21 at 17:51

Mangala Sadhu Sangeet S Khalsa

56
3

score 0 · Answer 49 · edited Nov 16 '12 at 12:41

0

In Xcode navigate to the Product menu and choose EDIT SCHEMES.

Verify that the Launch Automatically Radio Button is selected.

edited Nov 16 '12 at 12:41

Echilon

10,064
33
131
217

answered Jul 22 '11 at 16:37

Patrick

1

score 0 · Answer 50 · edited Nov 11 '12 at 11:09

0

I was trying to use the all solutions, but none worked for me. I realised that the problem occured, when Info.plist had set any Target Membership.

Try to check out all checkboxes in Target Membership (Utilities) of all files called Info.plist.

edited Nov 11 '12 at 11:09

Rimian

36,864
16
117
117

answered Sep 21 '11 at 11:24

maros

432
3
17

score 0 · Answer 51 · answered Oct 29 '11 at 12:42

0

"attaching to ..." issue:

xcode 4.1 solution: Make a new template app in xcode 4.1 and run it in the simulator. This resets the error and xcode-sim bridging correctly :)

answered Oct 29 '11 at 12:42

LondonRon

21
1

Didn't work for me. I was able to run another app in the simulator, but when I re-opened the problem project, it continued to have the same problem. – Tyler Collier Nov 03 '11 at 00:10

score 0 · Answer 52 · answered Dec 05 '11 at 07:51

I have had the same problem several times as well. Have tried all of the above suggestions, but the only that have worked for me, is to do a restart of my Mac. Seems like there are some process hanging.

If I where to know the name of it (it is not the my applications process) I would probably be able to just kill it, and not having to do the full restart.

FishStix · Answer 53 · 2012-03-15T00:24:23.123

0

I had tried everything. My "wrapper extension" was empty and the app wasn't getting installed in the simulator. I changed "wrapper extension" to "app" and it now installs in the simulator.

It's still hanging on Attaching to APP_NAME though...

EDIT Upgraded to Xcode 4.3, a couple more restarts and clean & builds and it's working now....

edited Mar 15 '12 at 00:24

answered Mar 14 '12 at 23:29

FishStix

4,994
9
38
53

score 0 · Answer 54 · answered Mar 29 '12 at 20:41

I had this exact same problem when running on lion with the newest version of xcode. It ran this "helpful" wizard to swap my project settings to use LLDB instead of GDB which I thought was fine.

It was not fine. For our project LLDB just refused to attach and then caused the project to hang without any error messages. Swapping back to GDB manually resolved the problem.

You can do this in "Manage Schemes"

Xcode 4 hangs at "Attaching to (app name)"

54 Answers54

Linked