This time we've got some good and some bad news. The good news first, iCamcorder v2.0 has been submitted to Apple at the beginning of this week. This update introduces new features and fixes the iOS 4.0 issues. Both the lite and the premium version have been submitted and we hope they're going to be available at the same time.
The iPhone 4/iOS4.0 update for our VAT-Calculator app has been approved and is now available on the App Store. It features iPhone 4 optimized retina display assets and fixes a compatibility issue with iOS 4.0.
Now to the bad news, Apple rejected the iWebcamera 1.5 update we submitted last week. Because we're using UIGetScreenImage. For us, this is totally annoying because UIGetScreenImage is not a private API since December 2009 and a lot of our apps have been using it since then.
Thank you for submitting your update to iWebcamera to the App Store. We've reviewed iWebcamera and determined that we cannot post this version of your application to the App Store because it is using a private API. Use of non-public APIs, which as outlined in the iPhone Developer Program License Agreement section 3.3.1, is prohibited:
"3.3.1 Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited)."
The non-public API that is included in your application is UIGetScreenImage.
If you have defined a method in your source code with the same name as the above mentioned API, we suggest altering your method name so that it no longer collides with Apple's private API to avoid your application being flagged with future submissions.
So, did we change our code? No, there is no other possible way of doing what we do on OS 3.0. We just resubmitted the same binary and wrote an email to the App Review team. This stuff is totally frustrating, working hard to get an update to the customers as soon as possible. It get's submitted to Apple and they reject it — for no reason!