If you're looking to get higher frame rates and general application performance tweaks from your iOS application, you may need to take a look at transparent settings on your subviews. Any time you set a subview to be transparent, the OS has to blend multiple layers together to figure out the end flattened result. This blending takes CPU cycles and can impact performance of your app - especially in something as simple as a UITableViewCell. ...
I spent the past week pulling out my hair trying to submit an update for Centare's EyeOnWeather application to iTunes Connect. I kept getting a reject from the system and all I got for an error message was "Invalid Binary." THANKS, THAT'S SOOPER. Eventually I ended up attempting to contact iTunes Connect Support for further details. I thought it might have been missing icons, malformed Info.plist, something. I haven't changed anything in the project drastically with how it builds, so I was at a loss. Turns out, I was picking the wrong provisioning profile in my setup. Man I felt stupid. Ends up that I'm not crazy - Apple's documentation on how to set up your project for building still only references Xcode 3. Awesome for the rest of the world using Xcode 4. Here are some tips I got from Apple iTunes Connect support for pulling in information to submit to their developer team: ...
I didn't start developing in Xcode "for real" until this year but I've played around with Xcode for a number of years. Over that time, I've screwed around with settings and changed defaults. It got to the point where following screen shot examples weren't matching up, #pramga marks in my code weren't showing up correctly in the code editor method drop down list and on and on. Perusing through Xcode Workspace Guide, I found this handy little suggestion from Apple: To reset Xcode to its factory settings for the logged-in user, run these commands in Terminal: ...
Xcode 3.2.1 was released today and is available for download with iPhone SDK 3.1.2. This release is mainly a bug fix release and I've confirmed it does fix the Unit Testing issue I reported earlier.
I haven't written unit tests before in Xcode. I started to read Apple's article on unit testing with iPhone development because I wanted to follow sound development principles with an agile approach. Not long into the guide, I got stuck. Literally. Using Xcode 3.2 on Snow Leopard caused Xcode to lock/hang during the build of the logical unit test. Same results after iPhone SDK 3.1 came out. I couldn't find anything online either except a few people experiencing the same issue. In the system console (not Xcode console) I was seeing: ...
Xcode has a build directory inside of your project, which you shouldn't be including in your source code management repository. Simply said, those files change so much and are "discardable". There is no way to easily exclude this directory from your repository. The accepted way to fix this (after some digging) is to simply move the build directory for Xcode to a temporary folder. To move the build directory, click on the Xcode menu in your menu bar, and click on Preferences. Change the folder under "Building" to a temporary folder. I created a tmp directory in my user folder. ...