It had to happen sooner or later.  The dreaded red light of rejection descended on one of my new application submissions.

They got me on the old “App Store Review Guidelines, Metadata section, 3.5: Small and large app icons should be similar, so as to not to cause confusion” gambit. (By the way, there is no need to read that twice, the seemingly grammatically incorrect wording above is straight from the e-mail I received as well as being on the App Store Review Guidelines web site. Go to to see for yourself after you have logged into your developer account.)

It is true, the 57×57 icons I used for the two applications were not just scaled down versions of the 512×512 images that I put on iTunes Connect, I wanted to use smaller images for the app icons, and scaling them up would have made for a couple of messy images for the iTunes App Store.

Strangely enough, I submitted these two similar applications at the same time, and the other one managed to make it through, despite the fact that the application’s 57×57 icon was not very similar to the 512×512 icon I uploaded to iTunes Connect.

Oh well. The offending app has been resubmitted, hopefully it will get approved before they take the Christmas break.

More iPhone code signing issues

Here’s a little nugget that I just learned about code signing your iPhone app that I probably was able to get around before by the  bumble-around-trying-everything-under-the-sun-before-stumbling-on-the-right-combination method.

Your build settings in the Target override your build settings in the project.

This is obvious to me now looking back at it, but I am very nearly 100% sure that this was tripping me up on the previous projects that I have tried to submit to the App Store.

It probably says this somewhere in the Apple documentation, but I am too tired to look for it to verify that it is in there.  Now if I can just get the UIAutomation tool in Instruments doing what I need it to do.  I used to remove the logElementTree function out of the js file after I figured out how deep something was buried in the hierarchy, but I got tired of retyping it so I just leave the line in there now and just move it down to the next block of new functionality I am trying to exercise.

Moving a SQLite database from device to simulator

I was working with my app on the device, and had built up some data that I wanted to get over to the simulator. Being the lazy developer that I am, I thought for sure that there should be a way to do this, and lo and behold, there is indeed.

To get the file from your device, open the Organizer window in Xcode, select your device from the left hand panel under Devices, and then find your application in the main part of the Organizer window under Applications. If you click the arrow next to your application, there should be an Application Data item that appears, and there is a down pointing arrow to the right. Click this arrow, and it will ask you to save the files from the device to a folder somewhere on your Mac hard drive.

Inside of this folder, you will see a Documents folder, and you should see your SQLite file there. You can then copy this file to the appropriate area for your simulator, which for me is:

~/Library/Application Support/iPhone Simulator/4.2/Applications/Your_application_UUID_here/Documents

After I copied the SQLite file to this location, I fired up the simulator, and all my data was there. Nice!