Hi folks - first thanks for all the posts, in building my first app got all but one question answered by simply trolling the forum. I got a rejection from Apple: We found that your app failed to launch on iPad 2 running iOS 4.3.3, on both Wi-Fi and cellular networks. We encountered the issue when selecting the application on the Home screen - the app displayed a launch image then quit unexpectedly. This may be because iOS 4 uses a watchdog timer for applications; if an application takes too long to complete its initial startup, the operating system terminates the application. For information about the watchdog timer, please see Technical Q&A: Application does not crash when launched from debugger but crashes when launched by user.. Another possibility could be a missing entitlement. For more information, please see the Technical Note: Resolving 0x800003A, applications not launching and missing entitlement. Now, first I might just release on iPhone only to get it out there. But maybe folks here have found a fix? No prob in the xcode 4 os simulator iOS release Deployment Target is for 3.0, while SDK is 4.3 BTv1.5 first downloaded as schooner haven't redownloaded source since clipper release (won't that replace my populated sounds list in appDelegate.m?)

You have a splash screen? What about the timing of it if you do? Is it waiting for a user click? What does the home screen go to? Just thinking out loud while I eat.

yes splash screen, 1 sec, and 1 sec fade so that users can get to the content quickly no wait for user click. i'm using a tabbed layout and the main screen is the core content the ipad splash screen png is only 668kb and is included in the binary (not dloaded from BT or other servers)... haha i should get some brekky too, late for day job!

This is the first time we've seen this report but it does make sense that Apple could complain if an app took too long to startup. Your app should launch pretty quick. Next, if it needs to, it will attempt to check for a 'last update' time from the backend. If new content is found (changes in the control panel mean new content) then it will re-download it's config data. This process can take a moment if there are lots and lots of things to download. There are lots of things that control how the update process works. Maybe have a look at the docs here http://www.buzztouch.com/docs/v1.5/index.php to see if understand it?

The comment seems to have been about iPad 2 only, I'm seeing if Apple can clarify if there was indeed no problem on the iPhone. In which case the testers should have experienced a similar need to refresh/update on startup on the iPhone and iPad 1, but apparently had no problem. Will update this post when I get a response...

I have an Ipad2 and be happy to assist you as tester if you need to. Let me know. Br/Stefan

Thanks for the responses David and MacApple, and for the offer Stefan! I'll let you know when I've got a version to test. In the meantime, I've resubmitted as an iPhone only app, since Apple's response to my clarification question was simply (paraphrasing) look at our previous response... uh thanks.

Good luck, keep us posted.

OK, after submitting as iPhone only app, I still get a crash and rejection as follows: --- 2.1 We found that your app crashed on iPhone 4 running iOS 4.3.4, which is not in compliance with the App Store Review Guidelines. Your app crashed on both Wi-Fi and cellular networks when we: 1) Launched the application 2) Tapped on any of the buttons 3) The application crashed We have attached detailed crash logs to help troubleshoot this issue. For information on how to symbolicate and read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports. --- I have two crash report files. This is now way beyond me. Besides redownloading the BT_Config.txt and replacing it in my original app folder; what else could I do? Thanks in advance! Reachable at [email protected]

Are you testing this thing before you submit it? It's a really bad idea to submit apps that don't work. I realize you didn't intend on this but asking Apple to be your tester's is a recipe for disasater. So..it's tough to say what's happening wihtout any details. Do this... a) Compile the app and launch the simulator. b) Open the console in Xcode. c) Lots of information will be output to the console to help you understand what's happening. d) Tap something or do whatever you can to try to get it to crash. When it crashes you'll hopefullly be able to see some details to point you in the right direction.