I'm running Xcode 4.1 (4B110) ad trying to upgrade to version 4.2 so I can test stuff on my iOS 5 iPhone and iPad. Trouble is the appstore says it is installed. Clearly it isn't. I've got an old version of 3.2.5 or something like that and this 4.1 version.
Anyone got any ideas. I just spoke to someone at Apple developer hotline who said:
"It might be a problem, I don't know. I can't even get to your details because we have no systems... Try again on Monday!"
So a nice quiet weekend for me unless anyone can help.
Ta.
Rob.
UPDATE:
Suddenly the appstore told me I had one update available... for Xcode 4.2
So now it's almost finished downloading (1.8G) for the second time and still nothing installed.
All installed fine once the download actually happened and downloaded twice for some reason (I think it did that last time as well).
In your application folder, you will find Xcode installer, run this and you will be fine!
Edit: I think it is called "Install xCode"
My further problem was that I already had "Install Xcode.app" (version 4.1.1) in my Applications folder, which prevented me from downloading the version 4.2 from Mac App Store. I deleted my existing Install Xcode.app, then I was able to download Install Xcode.app (ver 4.2), then I was able to update to Xcode 4.2
Related
Has anyone installed the latest concierge with the RedWeb SDK?
Since installing I can no longer save and have the program automatically compile the code. It will compile and then loops. Normally you save your file and it automatically compiles and responds with the ready and the localhost, etc... I have to kill the terminal session in VSC and restart a terminal session and do ngv run and it will work.
Note: This is the Concierge version released this week. We are developing specifically for RedWeb and not the desktop version which has a different SDK. Just curious if anyone is experience this with SabreRedWeb-SDK-21.5.5
I had issues with that version also. Sabre has just finalized version 21.6 SDK and it should be on the website soon. The newer version worked fine with all my testing so far.
Symptoms: Running any iOS 5.1 application from Xcode 4.4 (and 4.4.1) will launch the iPhone simulator but result in a plain black screen. In the Xcode console, the message "error: Failed to attach process to id " is displayed, being different each time. Attempting to 'Stop' the application from Xcode does nothing, and only Force Quit will return Xcode to a working state. Pressing the 'Home' button on the simulator shows that the app was successfully installed. Sometimes, opening the app from the simulator will show the UI, but no console messages are displayed, even after manually performing 'Product->Attach to process.'
Attempted Solutions: Xcode 4.3.x was originally installed on Lion, working charmingly. The problem started at installation of Xcode 4.4 in early August, for a project which was working before. I upgraded to Mountain Lion, didn't help. I reinstalled Xcode, didn't help. I upgraded to 4.4.1 Aug 7, didn't help. I deleted all trace of Xcode data, running: find / -name '[xX]code' and deleting all super-folders where it seemed relevant. That (not surprisingly) caused some OS issues, since subsequently reinstalling Xcode just didn't work. I then did it again, reinstalled Mountain Lion (to restore some OS files I probably killed), then reinstalled Xcode 4.4.1.
For projects, I typically ran new, single-view projects each time. Lately I've tried using this sample project from Apple, per link 3 below. I tried all the clean builds, etc., but honestly, one would assume opening a fresh project should just work. Just for kicks, I put a single 'Label' object in the iPhone storyboard at times.
After doing some homework I managed to find the following questions most similar to mine, but none are exact nor do any of the solutions work (in order of decreasing relevance):
xcode-4-4-ios-5-1-simulator-problems
crash-of-xcode-4-4-for-mac
failed-to-attach-to-process-id-xcode
unit-test-target-doesnt-run-on-xcode-4-5
xcode-4-4-freezing-on-project-close
simulator-keeps-crashing-in-xcode-4-4
Any help would be greatly appreciated. I apologize for the lack of brevity, but I've spent probably 15 hours trying to find/implement solutions to a seemingly trivial problem, and I would rather provide all relevant information than to have you guess at what I did. I'm not going to specify all the build info, just because it's whatever comes stock on the fresh install of Xcode.
I had similar problem (although with different configuration) and found incredibly simple solution by chance. I just used Product->Stop, then Product->Run (through keyboard shortcuts if that matters). Just once! Then the problem disappeared.
configuration: XCode 4.2, iPhone Simulator 5.0
symptom difference: process attaching didn't fail
It seems to me that the problem stems from the XCode-Simulator communication, and that's why I've shared my experience here despite the differences.
EDIT: It comes out Stop; Run didn't provide permanent solution for me. The problem is recurring from time to time. Still it is a temporary workaround for me.
I got this a few times, especially when I kept running my app and cancelling it or interrupting it too often, it's not something you can put your finger on, but yes I always managed to get back up and running by deleting the app in the simulator, cleaning project and build folder, deleting derived data (in Xcode organiser > projects view), restarting simulator and Xcode.
This also happened a few times on the device, and I needed to restart the device, iPhone in my case. I hope these infos help you out.
I got this to work by building and running the simulator using the Xcode 4.5 developer preview. I then closed it out and reopened Xcode 4.4.1 and it built and ran fine.
While none of the solutions above worked for me, thanks for putting this all together. I figured I'd answer here since this was the most comprehensive.
While this isn't exactly a solution, after today's OSX 10.8.1 update from Apple, this issue has been resolved. It's safe to say that some bug arose in the process of installing Mountain Lion and Xcode 4.4 that was fixed with this update to OSX.
I think I've cracked this one for my particular case, and I admit it's somewhat a mistake only newbies should do but I had overrided
viewWillApear:(bool)animated {}
in a ViewController of mine, without calling back
[super viewWillApear:animated]
It might be a good idea to search for all view lifecycle methods in your project and see if you have similar problem.
I've updated Xcode from 4.1 to 4.2 in Mac App Store but Xcode is still 4.1.
In Mac App Store now, no update available anymore. Xcode in Mac App Store does not appear like installed application because the button is labeled as "FREE" then "INSTALL APP" not "INSTALLED" as expected. When I clicked "FREE" and then "INSTALL APP", it alerts
"We could not complete you purchase
Xcode is already installed on this computer. Choose Software Update from the Apple menu to check for available updates."
I followed the instruction but there is no available update for Xcode. I also tried to restart my computer for a few times but no effect.
Edited: There is no Install Xcode in my Applications folder as well.
Is there any suggestion? Thank you.
Let me answer my question.
In my case, instead of Applications folder, Install Xcode appears in Launchpad. So if you cannot find Install Xcode in your Application folder, take a look at your Launchpad.
If I recall correctly 4.1 was before the mac app store and they may not have built in an easy way to cleanly update between the two. You could move the 4.1 app to your desktop temporarily and see if the 4.2 install will go through and install itself, or uninstall 4.1 completely (make sure your projects are not saved within). Or also see if in the mac app store it has a check for updates not the same as Software Update.
I created an empty Single View application using Xcode 4.2 on OSX Lion 10.7.2 targeting iPhone 5. The project built happily however when launching the simulator I receive the following error message:
iOS Simulator could not find the SDK. The SDK may need to be reinstalled.
I then tried targeting the iPad with the same results. I removed Xcode using the terminal and downloaded a fresh copy from the AppStore. The clean installation generates the exact same error.
It seems that the SDK is not being deployed during installation. Any advice or tips on how I can correctly install the iOS 5 SDK for the simulator to work?
Update
I downloaded the iOS 4.3 simulator which was not installed. The simulator works perfectly if I select the 4.3 SDK but for some reason is not recognizing the folder containing the 5.0 SDK.
Update
I reformatted the MacBook, reloaded a clean OSX Lion without restoring any backups and installed Xcode. Running the simulator directly after the installed worked, however after a reboot and relaunching Xcode the error came back. The SDK itself seems to have been corrupted. Will try and reinstall Xcode again.
After some testing it turns out the problem is caused by a 3rd Party Software. Recently the developer of TotalFinder removed the Asepsis portion of the system and created a separate application for the handling of DS_Store files.
Unfortunately, this breaks the iOS Simulator once installed, and even after uninstalling Asepsis, I needed to rebuild my whole machine to get rid of the error.
Update
BinaryAge is aware of the issue with regards to Xcode 4.2 and it is now listed on the know issues page and a warning banner displayed on the download link.
Final Update
It seems BinaryAge has changed the way Asepsis works and this is no longer an issue with the latest versions.
Did you try "File -> Reset Content and Settings ..." in the simulator ? I also encountered the similar problem, but it worked after I reset the simulator! In fact, I also found it worked after I removed all the existing projects and created new ones, but it occurred again after I restart xcode. Fortunately the "Reset" always works for me and I hope it can be helpful for your case.
I have this jailbroken iPhone 3G with iOS version 4.2.1 (the latest supported version). When I connect it to Xcode 4.2, Xcode starts copying the debug symbols. It stops copying towards the end of the process, and shows the following error:
Xcode has encountered an unexpected error (0xC002)
No such file or directory, at ‘/SourceCache/DTDeviceKit/DTDeviceKit-867/DTDeviceKit/DTDeviceKit_Utilities.m:864’
Anybody experiencing anything similar?
I know I should try and restore the phone, but I'm asking just in case anybody can come up with a solution that doesn't involve restoring it.
In this post on mactechnews.de, one guy reports the same problem -- with no solution, so far.
Alright, after a lot of testing and digging up the filesystem... I solved it.
It turns out that there are just a few files that are not downloaded from the device (for reasons still unknown). They are related to the dyld cache (don't really know what this is and what it's for). Here are the steps to make your 4.2.1 device debuggable in XCode 4.2 and 4.3.x:
Close Xcode
Go to: ~/Library/Developer/Xcode/iOS DeviceSupport/4.2.1 (8C148)/Symbols/System/Library/Caches/com.apple.dyld/ Note: if you don't have this folder, run Xcode, connect your device, and wait until the error 0xC002 appears in Organizer - the folder should be created by that time.
Create 3 empty files there called:
.copied_dyld_shared_cache_armv6
.processed_dyld_shared_cache_armv6
dyld_shared_cache_armv6
Run Xcode and enjoy the light next to your device eventually go green:)
Or, for the terminal lovers:
cd ~/Library/Developer/Xcode/iOS\ DeviceSupport/4.2.1\ \(8C148\)/Symbols/System/Library/Caches/com.apple.dyld/
touch .copied_dyld_shared_cache_armv6
touch .processed_dyld_shared_cache_armv6
touch dyld_shared_cache_armv6
This is obviously a hack but it works perfectly for debugging and I haven't noticed any side-effects so far.
Enjoy!
Small update:
I tested it on my snow leopard hackintosh, with the Xcode 4.2 (most recent to date) and although the device is active in the organizer and it is possible to run the app on the device, i get black screen on launch. It gets installed but apparently debugger cannot get attached. I had the same problem with 4.0.2, when the 0xC002 problem didn't yet occur so I think it's unrelated and might even not happen to others. Nevertheless, 0xC002 is still solved.
On my main development machine with Lion and Xcode 4.3.2, device is perfectly debuggable.
The answer above (https://stackoverflow.com/a/9944892/1390251) works, basically,
but for newer versions of Xcode you probably need to rename the files as follows,
having them end with '7' instead of '6':
touch .copied_dyld_shared_cache_armv7
touch .processed_dyld_shared_cache_armv7
touch dyld_shared_cache_armv7
If not sure, you can keep both sets of files (...6 and ...7)
in the relevant folder (can also be 5.1.1 for that matter)
and it should work.
(have tested it on iPhone 4 with iOS v5.1.1 genuine)
It seems that you cannot debug apps on iOS 4.2.1. I tried several restores to iOS 4.2.1 with same effect. Downgrading to iOS 4.0 was the only thing that worked.
The reason for whole problem is that iOS 4.2.1 is not supported in XCode, according to this website.
Error in Xcode getting debugging info from 5.0.1 iphone
solved, see the link to archive with iOS5.0.1 debug info
download & unpack to "~/Library/Developer/xCode/iOS DeviceSupport/" & be happy =)
I fixed this bug in![enter image description here][1] this way:
I duplicate the 5.1.1(9B206), rename it to 5.1.1(9A405)[my ios device is this version], then the error is gone.