Hi
My first app has been rejected today for private API usage with no precision. I'm using 0.81 version of cocos2D but i'm pretty sure it's not cause of that. I'm also using isimulate sdk which i forgot to remove in distribution product (sic). I think that's the problem but I'd like to know if somebody faced the same problem ? I don't want to send my binary and wait 10 days to be said the same thing...
App rejected for private API usage
(19 posts) (12 voices)-
Posted 1 year ago #
-
napierzaza
MemberYou should remove anything you don't need. There are also reports that people who created their own methods that coincidentally were named the same as a private API were flagged for using private APIs. So you should make certain that you don't have a method which is named similar to a Mac one. But you never know what their method names are!
Good luck.
Posted 1 year ago # -
This isimulate?
http://blog.vimov.com/2009/12/apple-shows-the-love-to-our-private-apis/
Thank you for submitting your update to iSimulate to the App Store. During our review of your application we found it is using a private API, which is in violation of the iPhone Developer Program License Agreement section 3.3.1; “3.3.1 Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs.” While your application has not been rejected, it would be appropriate to resolve this issue in your next update.
The non-public API that is included in your application is UITouch._touchFlags.
Please resolve this issue in your next update to iSimulate.
Posted 1 year ago # -
thanks
I removed isimulate and i will submit again tonight...@napierzaza : yeah that s a mess. I'll also ask apple by email some precisions
I didn't find much ideas on the web, except a possible problem with the "ccTouchEnded etc" methods.Posted 1 year ago # -
Some devs put out an app scanner that checks for private API's, it's 3 bucks, seems worth it.
Posted 1 year ago # -
I also got this when using 0.81 see my post
Posted 1 year ago # -
I am project manager of iSimulate. As finder39 said, iSimulate doesn't compile for the device. When you build your project for the device, the compiler deals with iSimulate library as if it does not exist. We already have thousands of clients using iSimulate (including ourselves ) and no one ever complained about this.
Posted 1 year ago # -
thanks,
@osama:SO that's bad news for me.
I don't really understand what I'm supposed to do.I found this (old template project code) in my project that might cause the problem:
-(void) onQuit: (id) sender
{
[[Director sharedDirector] end];// HA HA... no more terminate on sdk v3.0
// http://developer.apple.com/iphone/library/qa/qa2008/qa1561.html
if( [[UIApplication sharedApplication] respondsToSelector:@selector(terminate)] )
[[UIApplication sharedApplication] performSelector:@selector(terminate)];
else
NSLog(@"YOU CAN'T TERMINATE YOUR APPLICATION PROGRAMATICALLY in SDK 3.0+");
}Do you think it possible that code might be the problem ?
Posted 1 year ago # -
e-mail I received from Apple:
"The non-public API that is included in your application is terminate. If you have defined a method in your source code with the same name as this API, we suggest altering your method name so that it no longer collides with Apple's private API to avoid your application being flagged in future submissions."
Posted 1 year ago # -
"Terminate" is a private API call. I got flagged for this early this year.
Posted 1 year ago # -
@cj : Yeah it was the first one. Today i answer this email and ask if they can give me more precisions... Now, Waiting for reply
I removed my unused "onquit" method and try submitting. Hope . For the moment i can't figure out another method to modify.
For the curious, a trailer on my game :
Get the Video Widget Posted 1 year ago # -
Love the style! :D
Watch out for the flack on the app store when you allow cute characters to be killed. We got some negative reviews thanks to the exploding pig in our game ;)
Posted 1 year ago #
Reply
You must log in to post.