The Geek Blog » howto

Xcode 4 – Problem submitting App with Static Library

Aaron — Mon, 28 Mar 2011 01:12:16 +0000

I’m submitting a new version of my Migraine Diary App to the App Store and was running into problems with Xcode 4 giving me the following error: “[Your App Name] does not contain a single-bundle application or contains multiple products. Please select another archive, or adjust your scheme to create a single-bundle application.”

There is an issue or maybe it’s an intentional design thing with Xcode 4 and how it handles statically built libraries being included in your project. I’m specifically using Core Plot and it’s instruction set hasn’t been updated for Xcode 4 yet. Here are the things I had to do to get Core Plot to bundle correctly with my App to submit it:

Click on the Core Plot project which should be a child of your App’s project.
Click on the Project CorePlot-CocoaTouch and go to the Build Settings. Set “Skip Install” to Yes.
Click on the CorePlot-CocoaTouch target and set “Skip Install” to Yes.
Click Build Phases and under Copy Headers, move all of the Public and Private entries to the Project section.

You should then be able to build your project for Archive and submit to Apple.

Thanks to Apple Dev Forums – https://devforums.apple.com/thread/86137

iOS Basics – UINavigation Controller & Back Button Text

Aaron — Sun, 20 Mar 2011 15:16:09 +0000

I’ve brought an old project out of the moth balls recently, the Migraine Diary application I wrote as part of my master’s thesis. It was my first “real” iPhone app and I call tell I didn’t know what I was doing entirely looking through the code. What this has forced me to do, however, is re-learn some of the basics of iOS development and of Apple design patterns. I have been spending some time back in the Apple developer documentation and will probably be posting some of the gotchas that tripped me up two years ago and I’m solving now with the better, more elegant solution.

Navigation controllers are very useful things to have in your app, and are probably the easiest thing to implement WRONG. Two years ago, I assumed any time I needed a navigation bar up top that I needed to create a UINavigationController and make my view the root controller of it. Silly me.

One of the problems I was facing in the Migraine Diary app was changing the back button text when I was one or more levels deep into a navigation controller. My main view was titled “Journal Entries” and my child view “Journal Entry”. By default, the controller will title the back button as “Journal Entries” which you can see clutters up the screen.

I found a lot of ways of hacking the title online, but there is really only one “right way” according to Apple. The button titled “Journal Entries” is actually owned by the parent view. Before you push the child view onto the navigation controller, do something like this:

UIBarButtonItem *backButton = [[UIBarButtonItem alloc] initWithTitle:@”Back” style:UIBarButtonItemStyleBordered target:nil action:nil];
[[self navigationItem] setBackBarButtonItem:backButton];
[backButton release];

Take note that you’re referring to [self navigationItem] not [[self navigationController] navigationItem] since you are in the PARENT controller.

That’s it!

Loading a UIImage from a bundle

Aaron — Thu, 04 Jun 2009 00:33:36 +0000

I’ve been scratching my freaking head for an hour trying to figure out how to load an image from my application’s bundle. Doing this in Interface Builder is easy as pie, but not so straightforward.

[UIImage imageWithContentsOfFile:[[NSBundle mainBundle] pathForResource:@”thefilename” ofType:@”jpg”]];

Easy, isn’t it?