Xcode App Reviews

Please enable longer path for existing Project file to be added. If an existing project file path is long, you can’t add the project. For example “Something long folder name with long path/../../../In another long folder name with long path/Projectfile.xcodeproj"

Let’s just ditto the “Could not find developer disk image” 7.2 blindside. How many Apple developers are currently spinning wheels RIGHT NOW? Thousands? Apple, how about you hire an actual Apple iOS Developer. Keep him/her in the basement. Try out your new crap on said Developer first. If Developer cannot make anything work, DON’T DEPLOY IT.

So many people leave review here just to complain about one single issue they are facing. Ah, and also to whine about how awful is the current version comparing to previous one. But wait wasn’t the previous one so much worse than the one before it? If you read all the reviews you might think that Xcode gradually becomes worse and worse. Which is so not true. Let’s face it: nothing is perfect, there will always be issues, but overall Xcode is a great IDE.

Issue started when updated phone to iOS 9.3.1, Xcode started showing “Could not find developer disk image” Started update for Xcode 7.3, it keep spinning forever.

downloads but doesnt install

The new features are helpful and the whole platform is solid. I had absolutely no trouble upgrading from version 6 or installing it. It runs smooth on my MBP from 2013.

I really enjoy the apple developer experience. I am a solo startup developer who has already released 1 app and am starting development on a new one. As any developer will know, at the beginning of app development comes a lot of work. You can imagine my frustration of course when every other file that I click on in the hierarchy, crashes Xcode. My computer doesnt take long to start it back up again hwover it is the constant interuptions which bother me(10th one today). Please fix!

I was having trouble updating to 7.3 too. Here’s how I got it to work: 1. Update OS X. 2. Uninstall Xcode (go to launchpad, drag xcode to trash). 3. Reinstall Xcode. hope that helps!

I’m a student in college learning programming, and one of the languages we are going through right now is Swift. Since Apple is continually updating the lanugage to improve upon what they are building, it’s an interesting experience to say the least. One of my least favorite parts of this process has been this update process. I’ve been getting harassed by my iPad to update the software every time I open it to use it for classwork, and decided to just let it run so I could get through my work uninterrupted. After doing so, Xcode won’t recognize the device, telling me that it “Could not find Developer Disk Image.” Looking for support online, I’ve discovered that I have to update Xcode. Lo, and behold, Xcode will not update! The update will not even download! When removing the program from the applications folder, the computer tells me that I have the operating system. In order to update the Operating System, apparently my password isn’t good enough anymore. After updating my password on EVERY device that I own, I had to reverify my billing information. Now here I am, downloading this infernal upgrade to the operating system that I am being FORCED to download so that I can complete my school projects, and I am praying that it properly identifies the device that I haven’t had any troubles with in the past year and a half that I have been using it until I followed Apple’s harassing direction to update the system software. So, now that I have time to work on my project, instead of actually being able to troubleshoot my code and see if the MCBrowserViewController is working properly, I am sitting here jumping through endless hoops to fix something that WAS NEVER BROKEN TO BEGIN WITH.

I just got a band new macbook air out of the box. Xcode is always a major pain to update, so I thought I would get it out of the way and install it first. I just finally got it installed on my third try. This last time it had been bouncing back and fourth between “less than a minute” and “8 minutes” for about an hour. This is the install, mind you, not the download. And this is not a new issue. I shudder every time I see Xcode in my updates. I had hoped it would go better on a brand spanking new machine.

I have been using Xcode since I got my Mac in 2012. Amazing. When iOS 8 and Swift came out, I found that coding was a bit easier. Xcode 7.3 didn’t pop up in Updates until just now so I can’t tell you what developing for the new SDKs are like, so I’ll leave that up to you. 5 Stars. Awesome!

This application makes it so easy to use and learn how to code an application for apple devices! Keep up the great work Apple!

7.3 is pretty much not usable. Larger files can’t be viewed in the editor… Xcode continuously shifts the screen position up and down a few lines at a time every time it repaints/recolorizes the text. Worse yet, it doesn’t redraw the screen right when it does this, so I see half-line artifacts all over the place. It’s impossible to tell which line you’re on. Even after CTRL-L to redraw the screen, as soon as you start typing, it does the aforementioned scrolling bit, shifting you off the line you thought you were on, then drops the artifacts all over the screen so you can’t tell where it shifted you to. You can see the line numbers on the left side shifting up and down, while the actually code window either doesn’t change or becomes filled with artifacts. You can’t edit the same file in two windows, either. If you open a window to one function in a file and then open another window to another function in the same file, the first window becomes painfully slow. It takes several seconds for each keypress to appear on the screen. Autocomplete takes forever. Only recourse is to close the unresponsive window. Breakpoints aren’t working right either. I put them on one line, but the code halts several lines away. Redoing a clean build solves the problem for a while, but it comes back.

Compared to anything else out there, for any operating system, this is the best!

This version seems to need even more RAM than before, though I don’t see much of a benefit. In addition, when you run with Instruments you have to have very little else open. After I got the application memory warning, I closed everything and restarted the computer. Then I started Chrome (Gmail), Xcode, the Simulator, and Instruments and then got the warning again!! Finally I had to run with only Xcode, Simulator, and Instruments. Note, I have a 3.5 year old Macbook Pro, but this is beyond ridiculous. On a slightly different note, you are also almost guaranteed to never attach to the simulator the first time you run it after the simulator, or Xcode was closed. Whatever happened to the saving everyone 5 seconds speech Steve Jobs gave the first Mac team; that’s even more critical now? Guess Tim Cook et al just don’t care, unless you keep spending $$$$ on a new Mac(book) that has more RAM. Not everyone can afford the computer-equivalent of a BMW every few years. Apple’s iOS developers, and us, are expected to make great, bug free, tools that take up few memory and battery resources; guess Xcode developers aren’t held to the same high standard!!

This version seems to need even more RAM than before. In addition, when you work with Storyboard with it really takes lots time to even open it. Note, I have a 2 year old MAC and I have EL Capitain, but this is beyond ridiculous. It crash lots of time When I am working with Storyboard, On a slightly different note, you are also almost guaranteed to never attach to the simulator the first time you run it after the simulator, or Xcode was closed. Whatever happened to the saving everyone 5 seconds speech Steve Jobs gave the first Mac team; that’s even more critical now? Guess Tim Cook et al just don’t care, unless you keep spending money on a new Mac(book) that has more RAM and SSD hard disk. Not everyone can afford the computer-equivalent of a AUDI every few years. Apple’s iOS developers, and us, are expected to make great, bug free, tools that take up few memory and battery resources; guess Xcode developers aren’t held to the same high standard!!

buggy buggy buggy. It’s so temperamental, requiring repeated re-starts and long waits to process. I’m following an online tutorial, coding EXACTLY as it shows, but the output screen (when it even shows, much less updates changes) doesn’t make any sense. Just really frustrating. The Interface Builder seems to work as it should, but coding in the Playground is constant frustration and bugs.