Update: 2:42pm 11/13/11
Our new approach to working around the Apple scanning process is now available in all release branches on our continuous integration server. You may resubmit your applications using this build, as we believe this should address the issue – however, we are still in the process of testing this fix ourselves with a submitted app to verify that applications will no longer be flagged for “private API” usage.
Update 6:11pm 11/12/11:
We are aware that our first attempt at a fix did not succeed in addressing this issue. We have another attempt which we are going to test internally to see if it manages to avoid Apple’s ‘private API’ scanning. We apologize for this inconvenience, and it is most definitely our top priority to address this issue as soon as possible.
Recently, we have had some reports from the community about feedback from Apple that their recently submitted applications have contained the use of a private API, which is only identified as “layout”. While no Titanium applications make use of private APIs, we suspect that Apple has made changes to their application analysis tools which mistakenly flag this property in some Titanium applications.
To work around this flaw in Apple’s processing logic, we are making a new build available which avoids use of the “layout” keyword in Titanium’s own implementation logic. We are in the process of verifying this fix in the Apple App Store as we speak. To install and use this special build yourself, you can download and install it via the brief instructions below.
While in this instance the error is with Apple’s own processing logic, we want to make sure your app store submission process is as smooth as possible. If you have any additional questions or feedback on this issue, please contact me directly (kwhinnery at appcelerator dot com) and I will be happy to assist you.