Xcode 4.2 where is build directory

Xcode Unknown iOS detected. Xcode Build and Analyze broken for simulator. Installing multiple Xcode versions.

Setting iPhone Application Build Versions. The version of iPhone OS is too old. Xcode 4 developer preview now open to all developers. Tracking background memory usage of iOS 4 apps.

Xcode 3. Fixing Xcode default development region. Xcode Build Active Architecture Only. Xcode localization frustrations. Archiving builds with Xcode Organizer. Multiple Xcode targets and info. Downloading iPhone app data with the organizer. Zip the Application file and you should be fine. The Organizer window will open, and now you can select and "share" the archive. Otherwise, open the Preferences window and, under Locations, click the arrow next to the Derived Data pathname.

Your build folder is usually inside the derived data folder for this project. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. Asked 10 years ago. Active 10 years ago. Viewed 3k times. Must I set it in my Target or somewhere for it to create that folder? This is in Xcode 4.

Improve this question. Code files like. Resource files like. So, if the dropped files and folders are not in the 'Copy Bundle Resources' list, just drag it form the project navigator and drop onto the list. That will solve the problem. Then you can include files and folders as the 'Create folder references for any added folders' way. I experienced the 'stuck' problem every time when I attach files and folders as reference on Xcode 4.

Reinstalling mac was a useless effort for me. I have noted in Lion that when the iOS sim locks up or hangs the app, that if I go to a shell, and do ps -ef grep SDK , I will see many, many processes running associated with the simulator. I tried to kill off these processes but they rapidly respawn and the only solution then is to reboot.

Also, in the ps output, you will also see instances of your app running as well. So the Simulator issue is caused by previously running processes that appear to block the correct running of the latest one. I guess Apple will have a fix for this eventually, as it is quite onerous. Rebooting works for me, too, but this shouldn't be necessary.

I'd recommend filing a bug at bugreport. You can duplicate the one I created - the more it's duplicated, the more likely Apple is to fix the problem. I tried all of the solutions above but without luck When I search for simular problem here : Xcode error: failed to launch [directory] -- invalid host string: 'localhost'. Even if the app is not attaching after cleaning the project, changing the app name, restart the by resetting the simulator, and if you are using LLDB compiler, it is because the LLDB compiler is not able to connect to the local debug server in order to solve this, take a look at this.

Xcode 4. Now, this has been asked before: XCode 4 hangs at "Attaching to app name " and surprisingly, besides the accepted answer on that thread, there are at least 10 other possible solutions others have been adding, all for the same issue, people says one of them worked while the others didn't