Cocoaheads Ireland and Northern Ireland
After waiting 7 days my app went into 'In Review' status. 2 hours later it failed, judging server logs it was obvious the app hadn't even been launched by anyone, the failure was from an automated test.
The fail: One of my classes was acting as a delegate to a NSUrlConnection and that was all fine, I implemented the appropriate delegate methods, however I made the mistake of declaring the delegate method on my interface .h file. Force of habit, if I have implemented it, i tend to declare it on the iterface. Apple took this as a violation 2.5, Apps that use non-public APIs will be rejected. They thought I was trying to override or do something to one of their api's. As quick as I got the fail message I had xcode open, interface method declaration deleted, built, archived, validated and uploaded. Along with a nice message to the reviewer that I had very speedily done the change.
I had to wait another 7 days for it to be reviewed again. The next time it passed. As this was obviously an automated failure it is a pity that the itunes connect validation check did not pick this up. I know it tends to check whether correct signatures and profiles are there, as well as maybe Icons and what not, but when submitted for review you expect it to be reviewed on usability and its overall purpose.
But anyway not a problem now, but that was a long second 7 days.
App is available now, its called TwitF, and its an app for sending drawings over twitter just using your 140 character status updates, no 3rd party services or uploads. Check out www.twitf.com and http://itunes.apple.com/us/app/twitf/id496190487?ls=1&mt=8